> 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
Added to TODO:
* make CURSOR valid even after you hit end of cursor
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 1998-12-13 04:37:38|
|Subject: Re: [HACKERS] memory destruction in 6.4|
|Previous:||From: Bruce Momjian||Date: 1998-12-13 04:31:22|
|Subject: Re: [HACKERS] Parser bug (?)|
pgsql-interfaces by date
|Next:||From: Bruce Momjian||Date: 1998-12-13 04:44:17|
|Subject: Re: [HACKERS] PgAccess version 0.93 (for Unix and Windows) has been released!|
|Previous:||From: Hubert de Fraysseix||Date: 1998-12-12 18:11:49|