Re: more anti-postgresql FUD - Mailing list pgsql-general

From Merlin Moncure
Subject Re: more anti-postgresql FUD
Date
Msg-id b42b73150610160631g159a3cf7td98fd9bf44e2159@mail.gmail.com
Whole thread Raw
In response to Re: more anti-postgresql FUD  (Alban Hertroys <alban@magproductions.nl>)
List pgsql-general
On 10/16/06, Alban Hertroys <alban@magproductions.nl> wrote:
> Merlin Moncure wrote:
> > for server side browsing use cursors or a hybrid pl/pgqsl loop. for
> > client side, browse fetching relative to the last key:
> >
> > select * from foo where p > p1 order by p limit k;
>
> This does require some way for the client to keep a single transaction
> open. If this kind of query is performed by a web application (as is
> often the case), the "client" is the server side web script engine, and
> not all of those beasts are capable of keeping a transaction open across
> pages (PHP comes to mind).
> This combined with expensive (complex) queries is regularly a pain.

Server-side browsing requires transactions so is unsuitable for
certain types of web enviroments.  However client-side following as I
described as not...it is the right and proper way to solve this
problem .  It's also why the sql row-wise comparion is so important,
because it provides an easy way to do this with table with mutiple
part keys.

merlin

pgsql-general by date:

Previous
From: "Harald Armin Massa"
Date:
Subject: Re: Fast backup/restore
Next
From: DXScale452
Date:
Subject: ERROR: current transaction is aborted, commands ignored until end of transaction block