Re: Critical Bug with UseDeclareFetch in development version - Mailing list pgsql-odbc

From Dave Page
Subject Re: Critical Bug with UseDeclareFetch in development version
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9EFC@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Critical Bug with UseDeclareFetch in development version  (Marko Ristola <Marko.Ristola@kolumbus.fi>)
List pgsql-odbc

> -----Original Message-----
> From: Marko Ristola [mailto:Marko.Ristola@kolumbus.fi]
> Sent: 06 September 2005 20:17
> To: Hiroshi Saito
> Cc: Dave Page; pgsql-odbc@postgresql.org; Anoop Kumar
> Subject: Re: [ODBC] Critical Bug with UseDeclareFetch in
> development version
>
> Now it just understands, that the FETCH returned two rows,
> and after the two rows, it will not fetch more rows anymore.

Yes, I can confirm this. A cursor is used to retrieve the first N rows
(where N is the value of the 'fetch' parameter), but doesn't then get
any more when requested.

Anoop, Sivakumar - I guess this is fairly trivial for one of you to fix
(I'm not familiar with that part of the code). I guess it's just a case
of fetching the next 'fetch' rows when the last one or, for example, the
one at fetch/10 from the end of the set is accessed by the client. Can
you look at it please?

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Using Which Driver [correct]
Next
From: "Dave Page"
Date:
Subject: Re: notice handler in libpq-based driver