> -----Original Message-----
> From: Firebird-Architect@yahoogroups.com
> [mailto:Firebird-Architect@yahoogroups.com] On Behalf Of Vlad Horsun
> Sent: 14. juni 2005 08:32
> To: Firebird-Architect@yahoogroups.com
> Subject: Re: [Firebird-Architect] Can we, can we, can we????...
>
> > > User, even very experienced, can't prognose such things as
> > > number of fetches (or page reads). Statement execution
> time however
> > > is usually known to him. At least he can say for sure about upper
> > > time limit after which statement execution must be stopped.
> >
> >
> > The kind of user who knows what to expect from a statement doesn't
> > write statements that use unreasonable amounts of system
> resources. A
> > solution that relies on fools recognizing their own
> foolishness is not
> > going to succeed.
>
> Everyone make mistakes and can, for example, miss one of
> the join criteria producing cross join instead of inner join
> and endless execution as result. Only thing we can do is
> shutdown database for now.
>

But such problems will be caught in the design phase and/or function test
phase, won't it? I see little use of a forced timeout when an
application/database is put into production. A way to manually cancel a
query would be useful though.

/smn