Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.9.1/8.9.1) with ESMTP id OAA10612 for ; Mon, 7 Dec 1998 14:52:19 -0500 (EST) (envelope-from daveh@insightdist.com) Received: from insightdist.com (root@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id OAA23176 for pgsql-interfaces@postgreSQL.org; Mon, 7 Dec 1998 14:34:39 -0500 (EST) Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA34992; Mon, 7 Dec 1998 14:16:53 -0500 Received: from daveh by ceodev (AIX 4.1/UCB 5.64/4.03) id AA23262; Mon, 7 Dec 1998 14:14:23 -0500 Message-Id: <366C2A36.32C53DB7@insightdist.com> Date: Mon, 07 Dec 1998 14:19:18 -0500 From: David Hartwig Organization: Insight Distribution Systems X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en Mime-Version: 1.0 To: PostgreSQL-development Cc: pgsql-interfaces Subject: Cursor Movement - Past the End 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. TIA.