Subject | Re: [IBO] How to clean up resources at closing program ? |
---|---|
Author | Helen Borrie |
Post date | 2003-08-18T13:39:13Z |
At 03:24 PM 18/08/2003 +0200, you wrote:
first.
In Firebird you can't stop a running query, so if there's an executing
query, it has to wait for that to finish. (I don't know if IBO has yet
caught up with IB 7's ability to stop a running query.)
Once all datasets and executed statements are ready to commit, it tries to
commit the transaction(s). Any that fail, it rolls them back. Then, any
prepared statements are unprepared.
Helen
>Thanks, Helen that was very clearIf there is a dataset that has unfetched rows it will finish fetching them
>
>One small question though
>
> > OK, the "bomb-proof" creation order is to create the session first, then
> > the connection, then the transactions, then the datasets.
>
>If I use the automatic cleanup that happens with this order,
>I suppose, that when a transaction still is running the cleanup will wait
>till the transaction has finished is that correct ?
first.
In Firebird you can't stop a running query, so if there's an executing
query, it has to wait for that to finish. (I don't know if IBO has yet
caught up with IB 7's ability to stop a running query.)
Once all datasets and executed statements are ready to commit, it tries to
commit the transaction(s). Any that fail, it rolls them back. Then, any
prepared statements are unprepared.
Helen