Is there a feasible way to implement setQueryTimeout() accurately? Would executing queries in separate threads help if setQueryTimeout was used? (setQueryTimeout() is not supported yet.) How do other databases implement setQueryTimeout()?
Regards,
Ali



At 11:28 PM 12/22/2004, you wrote:
Suavi Ali Demir wrote:
So, does this mean Derby always launches a separate
thread to process a query?

No, just that it binds the current connection context to the thread (using a ThreadLocal) so that a lookup of "jdbc:default:connection" can return a connection to it. Statements in Derby execute using the invoking thread.


--
Jeremy



Reply via email to