Subject | Cancel long query by regular user |
---|---|
Author | Valeri Mytinski |
Post date | 2009-05-13T13:58:38Z |
How to cancel long query from application in that situation:
1) Application creates first connection with name&password of
regular user. Application is allowed to connect only with
regular *Firebird* users, not SYSDBA.
2) User enter data and application starts long SELECT query on
first connection.
3) User see that he/she made error in data and wants to cancel
long query.
Application can't start another query (DELETE from mon$statements)
on first connection while SELECT is running. Or can?
Application may create second connection with same user&password,
but rows in mon$statements table for first connection is not
visible by second and can't be deleted.
How you solve such problems?
Regards,
ValeriM
1) Application creates first connection with name&password of
regular user. Application is allowed to connect only with
regular *Firebird* users, not SYSDBA.
2) User enter data and application starts long SELECT query on
first connection.
3) User see that he/she made error in data and wants to cancel
long query.
Application can't start another query (DELETE from mon$statements)
on first connection while SELECT is running. Or can?
Application may create second connection with same user&password,
but rows in mon$statements table for first connection is not
visible by second and can't be deleted.
How you solve such problems?
Regards,
ValeriM