I'm running mostly firebird 1.0.* in production/development situations, and I've known for a long
time that a long-running query will continue to run even after the client that requested it has
disconnected. Is there any particular way to get firebird to automatically stop those queries as
soon as it sees that the client has disconnected, or shortly after? I remember that firebird polls
each connection every few (180?) seconds to make sure the client is still there, to get around the
fact that tcp/ip connections can remain "active" with no data across them for hours or days at a
time (depending on the OS) ... can firebird pick up on a non-response and cancel the query?

I seem to remember "10 minute delay" getting mentioned at some point, but I'm not seeing that
happen, and it's a bit long anyway. I also remember some mention of having virtual tables available
inside firebird from which you could issue commands to terminate a query or transaction (if
SYSDBA) -- but that's not terribly automatic.

For my work-related win32 app, it's not too much of a concern ... but for my web-based stuff, it's
a bit more important. (And I've got mysql users laughing at me, as php will detect a client
disconnect and cancel connections to running queries, which mysql responds to ... or so they claim.
I'm not ever touching mysql again with a ... really long pole.)

-Philip