If i can start general discussion.. do you really use such feature in real systems? I saw this in MSSQL environment and what was advice of DBA when someone reach timeout? Increase timeout settings...
Kiling statement or transaction is not good as a general solution It must be customized for situations. I suppose better feature will be "timeout messaging" - something like TRIGGER ON STATEMENT_TIMEOUT TRIGGER ON TRANSACTION_TIMEOUT and inside it we have access to MON$ tables and we can cancel statement, transaction if we need. Inside we can check e.g. individual context variables which eovercome some default settings. We can post event and some admin client application can take some action i suppose you can run into more samples P.S. What about statements executing query to external database by EXECUTE STATEMENT? regards, Karol Bieniaszewski ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
