Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> The PostgreSQL team members (me included) are big fans of
> portability. Introducing code that solves a problem for one specific web
I don't see how this is web server specific?
> in the special case of a small number of application users,
Actually, I'm not sure that this should bother you. As I wrote
previously: I can put just the same load on the database server
using Java applets right now. In fact, the load with applets would
even be higher, as the database server does not receive any hint
when the connection is idle for some time...
> in a non portable way for only a couple operating systems
I get this point.
> and where the resulting functional difference is visible to the
> database client ...
If it wasn't visible, then it would be useless for me.
> I don't think this idea has much of a chance to make it into the
> source tree.
I'm disappointed, though, and summarize:
PostgreSQL transactions cannot be used naturally with CGI/PHP, and
virtually every web application out there is prone to lost updates.
Thank you very much for your feedback anyways.
In response to
pgsql-interfaces by date
|Next:||From: Jan Wieck||Date: 2004-12-17 17:41:02|
|Subject: Re: Lost updates vs resumable connections/transactions|
|Previous:||From: Andreas Kretschmer||Date: 2004-12-17 16:52:00|
|Subject: Re: plpgsql errorcodes|