From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199812130434.XAA14173@candle.pha.pa.us>
Subject: Re: [HACKERS] Cursor Movement - Past the End
In-Reply-To: <366C2A36.32C53DB7@insightdist.com> from David Hartwig at "Dec 7,
	1998  2:19:18 pm"
To: daveh@insightdist.com (David Hartwig)
Date: Sat, 12 Dec 1998 23:34:19 -0500 (EST)
Cc: hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> 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.

Added to TODO:

	* make CURSOR valid even after you hit end of cursor

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026