Subject | Re: [IBDI] 6.5 released |
---|---|
Author | Paul Reeves |
Post date | 2001-12-05T16:06:09Z |
Dmitry Kuzmenko wrote:
if it can interrupt execution. We can stop fetching at any time, although most
client tools don't surface that feature.
The new feature may require using another connection to kill a query, but this
seems to be an awful hack if that is the case. For instance, it would require
knowing the statement handle you wanted to kill. Just how would one 'know'
programmatically speaking?
Paul
--
Paul Reeves
http://www.ibphoenix.com
taking InterBase further
>Yeah, I was just wondering about this myself. The only point of DSQL_cancel is
> > > Asynchronous Statement Cancel - Gives users the ability to cancel
> > > an executing DSQL statement via the InterBase API.
> >
> > AFAIK, it was implemented for v6.0 but hasn't been properly tested to be
> > released in that time. Now Borland employees have completed this work.
>
> I don't think so. I don't beleive in it. Client api stalls at
> isc_dsql_execute until server will finish query and be able to send
> records to client. I think query canceling can be done only
> a) from another connection
> b) with services api
>
if it can interrupt execution. We can stop fetching at any time, although most
client tools don't surface that feature.
The new feature may require using another connection to kill a query, but this
seems to be an awful hack if that is the case. For instance, it would require
knowing the statement handle you wanted to kill. Just how would one 'know'
programmatically speaking?
Paul
--
Paul Reeves
http://www.ibphoenix.com
taking InterBase further