From: David Hartwig <daveh@insightdist.com>
To: PostgreSQL-development <hackers@postgreSQL.org>
Cc: pgsql-interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Cursor Movement - Past the End
Date: Mon, 07 Dec 1998 14:19:18 -0500
Message-ID: <366C2A36.32C53DB7@insightdist.com> (raw)
We are in the process of implementing several additional Extended Fetch
capabilities into the ODBC driver. In order to complete the full set of
functions, we need to be able to FETCH to the end of the cursor, detect
the end, and then be able to move to prior positions in the the cursor.
The problem is that once the end of the cursor is reached the cursor is
no longer usable.
I think the cursor should still be valid after moving past the end. I
have tinkered around to see if the cursor can be preserved after
moving/fetching past the end without much luck. I am throwing this
out to the list in the hopes that someone will respond "Gee, Dave, all
you have to do is (*^%^$$%$#!)".
I would greatly appreciate any assistance in resolving this problem.
Many ODBC components and applications make heavy use of these extended
features.
TIA.
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-interfaces@postgresql.org
Cc: daveh@insightdist.com, hackers@postgreSQL.org
Subject: Re: Cursor Movement - Past the End
In-Reply-To: <366C2A36.32C53DB7@insightdist.com>
* 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