From: | Christoph Haller <ch(at)rodos(dot)fzk(dot)de> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Cc: | wdarmst(at)bacchus(dot)com(dot)au |
Subject: | Re: Porting from db2 problem |
Date: | 2003-02-24 09:30:16 |
Message-ID: | 3E59E628.ED83D72@rodos.fzk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
>
> I am trying to port an app that currently runs over db2 and oracle
(on windows
> os/2 linux hpux aix etc) to also run over postgres.
> I am currently porting the windows client (using odbc).
> I am having major problems because of the lack of with hold cursors
(cursors
> that remain open over a commit) in postgres. There are a lot of places
where
> the app will - open a cursor with hold - fetch the first 20 or so
rows, allow
> the user to scroll thru the result set, updating and commiting changes
to
> particular rows as they go. When the user gets to the end of the
current set of
> fetched rows - the app will fetch the next 20 or so during a scroll
down
> operation etc. The user may hold the read-only cursor over the
result-set all
> day, and it is important that rows that they do update, be immediately
> available for other users.
>
> What do folk do to support this kind of scenario in the abscence of
with hold
> cursors ?
Have a look at SELECT ... FOR UPDATE ... LIMIT ... OFFSET ... ;
> Is implementation of with hold cursors likely in the near future?
>
I have no idea. Sorry.
Regards, Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2003-02-24 13:24:21 | Re: Help with query involving aggregation and joining. |
Previous Message | Josh Berkus | 2003-02-24 06:46:05 | Re: Help with query involving aggregation and joining. |