
> So the work that would need to be done is asking the driver to request the
> timeout via "BEGIN WORK TIMEOUT 5"; getting the backend to parse that
> request and set the alarm on each query in that transaction; getting the

Well imho that interpretation would be completely unobvious. 
My first guess would have been, that with this syntax the whole transaction 
must commit or rollback within 5 seconds.

Thus I think we only need statement_timeout. ODBC, same as JDBC wants it at the 
statement handle level. ODBC also provides for a default that applies to all 
statement handles of this connection (They call the statement attr QUERY_TIMEOUT,
so imho there is room for interpretation whether it applies to selects only, which 
I would find absurd).

Andreas

Tue, 2 Apr 2002 11:12:27 +0200
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: timeout implementation issues