Leyne, Sean wrote:

>This means that the real need is for elapsed time, not number of
>reads/fetches, not CPU time.
>
>
>
>

The state purpose of the request was to catch "bad" requests, not relief
from bored users. Maybe we're talking about one thing here, maybe two.

As mentioned, the problem with bored users killing long requests is that
they invariably restart them, wasting all of the resources expended so far.

If the problem is bored users, isn't the better solution a SQL analog of
the isc_unwind_request call? That would let an application developer
put a nice red "stop" icon on the tool bar for when tedium overwhelms
the users, putting request cancellation under application control.

--

Jim Starkey
Netfrastructure, Inc.
978 526-1376