Subject | Re: [IBO] Re: support for 2 transactions in ib_query |
---|---|
Author | Daniel Rail |
Post date | 2004-07-06T10:40:48Z |
Hi,
At July 5, 2004, 22:31, Mihai Chezan wrote:
to 500, because Firebird doesn't know what scrollable/positionable
cursors are and only has unidirectional/non-positionable cursors.
Which means that for an application to position itself on record no.X,
it has to fetch all the rows leading up to that record.
This has been discussed on Firebird's development list a few times,
even recently. It is not a high priority for FB 2.0, but might have
more interest for FB 3.0. Unless, someone pays for the development, or
does the implementation themselves and contributes the code.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)
At July 5, 2004, 22:31, Mihai Chezan wrote:
> Anyway, the bottom line is that for Refresh to get only the key columsIt doesn't have a choice to fetch all the key columns for record no.1
> from the server you have to set FetchWholeRows := False.
> But even so, ibo will fetch the key columns from record 1 to record
> 500 (if you set FetchWholeRows := False in my test demo) and not only
> the key columns that are visible in grid (rows 496-500).
to 500, because Firebird doesn't know what scrollable/positionable
cursors are and only has unidirectional/non-positionable cursors.
Which means that for an application to position itself on record no.X,
it has to fetch all the rows leading up to that record.
This has been discussed on Firebird's development list a few times,
even recently. It is not a high priority for FB 2.0, but might have
more interest for FB 3.0. Unless, someone pays for the development, or
does the implementation themselves and contributes the code.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)