Hi all.
I couldn't confirm, that the memory behaviour is good
for Declare/Fetch.
My tests lost memory about 125M, but
the behaviour should be good with forward only
cursors (about 5M proccess memory).
Without Declare/Fetch query result consumed 40M memory (600000 rows fetch).
I used Fetch=2, because it tells the worst behaviour.
So the idea with Declare/Fetch is that the memory footprint with the
process is constant,
while reading millions of rows from the database.
Regards,
Marko Ristola
Dave Page wrote:
>Hi Marko,
>
>I just committed a fix for this which passes your test program, and a
>variety of manual tests in the MS ODBC test program.
>
>Basically what was happening was that each set of results was read into
>the same block of cache, but when it extracted the values to send to
>copy_and_convert, it assume that each tuple was offset by the total
>number of tuples from the start of the cache, where it was actually
>offset by the tuple number within that set. If that makes sense :-).
>
>Can you give it a whirl please?
>
>Regards, Dave.
>
>