Subject | Re: [firebird-support] Firebird 2.1.2 Cancel Running Query |
---|---|
Author | Helen Borrie |
Post date | 2009-04-20T05:01:04Z |
At 02:14 PM 20/04/2009, you wrote:
2. A statement can't be cancelled if it is not active. Monitoring runs in a transaction. This means that a statement that's inactive at the time your monitoring transaction starts [think "started"] will be invisible. So commit your old monitoring transaction before trying to do something fresh.
Otherwise - maybe that bad statement simply beats you to it
./hb
>Hi1. You could only do that if you called it from a login that was either SYSDBA/root or the same *Firebird* user as that which owns [AnotherAttachment]
>
>With Firebird 2.1.2 classic server, I use the following SQL to delete running queries from another connection. It works as expected on Windows server - an 'operation was cancelled' exception was raised. But with a Linux server, it doesn't seem to have any effect on the running query.
>
> delete from mon$statements
> where mon$attachment_id = [AnotherAttachment]
>
>Am I missing something here?
2. A statement can't be cancelled if it is not active. Monitoring runs in a transaction. This means that a statement that's inactive at the time your monitoring transaction starts [think "started"] will be invisible. So commit your old monitoring transaction before trying to do something fresh.
Otherwise - maybe that bad statement simply beats you to it
./hb