I believe that the functionality is implemented correctly. In terms of engine SQL statement must be completed to stop the timer, if it is a select query to include fetches of all records. This is in good agreement with the new strategy for the garbage collection READ COMMITTED transactions, and DBA allows you to control whether the "bad" queries.
In the original version of the discussion offered a timeout on the client side. The fact that Mark Rotteveel offers quite possibly more correctly implemented on the client side, but this implementation does not help developers JDBC and ADO .NET drivers because they do not use fbclient. -------------------------- The best regards, Simonov Denis ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel