Subject | Re: [IB-Architect] Long query |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2002-01-16T05:08:28Z |
On 16 Jan 2002 at 0:47, Helen Borrie wrote:
is interesting even here.
AFAIK isc_dsql_execute2() won't return until the query
execution is complete and the first row of the result set
is ready for fetch. So, we have to call something like
isc_break_execute() from a different thread.
What is more "right" - make programmers to use multi-
thread architecture or add "asynchronous calls" to API?
(When an isc_dsql_execute_nowait() returns immediatelly and
calls a callback function after the result is ready. In
this case an isc_wait() may be good too. Oracle uses this
method.)
BTW, how this feature is implemented in IB6.5?
SY, Dmitri Sibiriakov.
> OK, this group is NOT for support questions.Of course, the question was wrong. But subject (I think)
is interesting even here.
AFAIK isc_dsql_execute2() won't return until the query
execution is complete and the first row of the result set
is ready for fetch. So, we have to call something like
isc_break_execute() from a different thread.
What is more "right" - make programmers to use multi-
thread architecture or add "asynchronous calls" to API?
(When an isc_dsql_execute_nowait() returns immediatelly and
calls a callback function after the result is ready. In
this case an isc_wait() may be good too. Oracle uses this
method.)
BTW, how this feature is implemented in IB6.5?
SY, Dmitri Sibiriakov.