> -----Original Message-----
> From: Firebird-Architect@yahoogroups.com
> [mailto:Firebird-Architect@yahoogroups.com] On Behalf Of Nando Dessena
> Sent: 13. juni 2005 19:18
> To: Firebird-Architect@yahoogroups.com
> Subject: Re: [Firebird-Architect] Can we, can we, can we????...
>
> Ann,
>
> A> How does one allow your important,
> A> well-designed, but necessarily long queries to run while
> killing my
> A> badly thought-out full-cross product hack? If the parameter is on
> A> the connection, how do you insure that all idiots use the
> A> kill-my-query option? If on the database, how do you be
> sure that we
> A> don't fall into the Hitch-hikers Guide trap and kill the
> query that's
> A> 2 seconds from giving us the ultimate question to the
> ultimate answer?
>
> It looks like the only option that's flexible enough is
> having the ability to set a database- or connection-wide
> optional timeout, and also the ability to set one (or disable
> the default one) at statement prepare time.
>
> But all in all I feel that a way to identify and kill a
> particular request would cover all this and more, so why
> settle for less?
>
> Ciao
> --
> Nando Dessena

I agree. A way for the client to terminate a query would be very nice. I
fear that a system wide timeout in many cases would cause more frustration
that it solves. Connection wide and statement wide timeouts would be OK as
long as the default is infinitive.

/smn