From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Marko Ristola" <Marko(dot)Ristola(at)kolumbus(dot)fi>, "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
Cc: | <pgsql-odbc(at)postgresql(dot)org>, "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>, "Sivakumar K" <sivakumark(at)pervasive-postgres(dot)com> |
Subject: | Re: Critical Bug with UseDeclareFetch in development version |
Date: | 2005-09-07 08:10:03 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9EFC@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Marko Ristola [mailto:Marko(dot)Ristola(at)kolumbus(dot)fi]
> Sent: 06 September 2005 20:17
> To: Hiroshi Saito
> Cc: Dave Page; pgsql-odbc(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-09-07 08:38:06 | Re: notice handler in libpq-based driver |
Previous Message | Dave Page | 2005-09-07 07:40:56 | Re: Using Which Driver [correct] |