| Subject | Is there a way to determine implied cursor result set size ??? |
|---|---|
| Author | Dimitry Sibiryakov |
| Post date | 2002-11-12T03:53:45Z |
On 8 Nov 2002 at 12:46, Robert S. Sciuk wrote:
set is cached in temporary files (PLAN SORT) and impossible in all
other cases. When the engine scans table record by record returning
them one at a time (isc_dsql_fetch()), nobody knows how many records
left. If the transaction isolation level is not REPEATABLE READ,
other users may add or delete records while you are getting your data
and any estimation will became wrong.
SY, Dimitry Sibiryakov.
>I'm using the Firebird 1.0 dsql API to embed an application, and withFrom my point of view it is possible theoretically if whole result
>the isc_dsql_execute() and isc_dsql_fetch() API's in an embedded
>application, and in looking at the Interbase 6.x docs, and scanning
>the web site, I see NO way to determine in advance the number of
>tuples in the active result set size.
set is cached in temporary files (PLAN SORT) and impossible in all
other cases. When the engine scans table record by record returning
them one at a time (isc_dsql_fetch()), nobody knows how many records
left. If the transaction isolation level is not REPEATABLE READ,
other users may add or delete records while you are getting your data
and any estimation will became wrong.
SY, Dimitry Sibiryakov.