From: Wayne Armstrong <wdarmst@bacchus.com.au>
To: pgsql-sql@postgresql.org
Subject: Porting from db2 problem
Date: Sun, 23 Feb 2003 22:11:38 +1100
Message-ID: <200302231113.h1NBDDkw021944@mail.bacchus.com.au> (raw)
Hi,
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 ?
Is implementation of with hold cursors likely in the near future?
Regards,
Wayne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: wdarmst@bacchus.com.au
Subject: Re: Porting from db2 problem
In-Reply-To: <200302231113.h1NBDDkw021944@mail.bacchus.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox