Subject | Is there a way to determine implied cursor result set size ??? |
---|---|
Author | Robert S. Sciuk |
Post date | 2002-11-08T17:46:56Z |
TWIMC,
I'm using the Firebird 1.0 dsql API to embed an application, and with 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.
Is there a way of doing this prior to having cached the entire result set
in the application?? It would be the equivalent to the PostGreSQL
PQntuples() call -- if that makes any sense to anyone.
I apologize in advance if this is an FAQ, but I've never seen it on any of
the web resources I've scanned (quite a few, actually). Doc pointers
would be very welcome!
Just wondering.
Cheers,
Rob.
I'm using the Firebird 1.0 dsql API to embed an application, and with 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.
Is there a way of doing this prior to having cached the entire result set
in the application?? It would be the equivalent to the PostGreSQL
PQntuples() call -- if that makes any sense to anyone.
I apologize in advance if this is an FAQ, but I've never seen it on any of
the web resources I've scanned (quite a few, actually). Doc pointers
would be very welcome!
Just wondering.
Cheers,
Rob.