> -----Original Message-----
> From: Firebird-Architect@yahoogroups.com
> [mailto:Firebird-Architect@yahoogroups.com] On Behalf Of Vlad Horsun
> Sent: 14. juni 2005 10:39
> To: Firebird-Architect@yahoogroups.com
> Subject: Re: [Firebird-Architect] Can we, can we, can we????...
>
> > > 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.
>
> Don't forget - we deal with database. Database at design
> time and database in production is a two (very) different
> things. Not all problems can be seen at development time.

That depends on how you test your product don't it?

> even if timeout useless in production - why can't we do it
> for developers ?

That is true. I'm just worried about the general usefulness of such a
timeout. If it is good enough to catch real problems then I would think that
also will terminate queries that are allowed to have long duration.


/smn