> A. Bill Meaney (application developer): I agree with FBServer. If I had a
> way to kill a running query, I could decide the right time. I could

present

> a Stop button to my users so that they could control "their" time. For
> background queries, those not initiated by the user, I could start a timer
> thread with what ever I thought was a reasonable amount of time and then
> issue a stop if needed.

What about - for example - web applications that run a query.

Would be nice to get a time-out if the "server is busy" and reply with a
"server is busy, please try again later" page instead of hanging for over
5 minutes and letting the user (they do this) do a "refresh page" and
claiming all available pooled connections with the same long running
query...

The point is: not everything can have a "cancel" button.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com