db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: Thread Interruption in large Database
Date Tue, 17 Jun 2008 02:39:39 GMT
PhilCope <phil1.cope@ge.com> writes:

> I would not expect setQueryTimeout() to help me - my observation is
> that executing the query doesn't take very long, it is the retrieval
> of the first result via the next() call that takes the time. Or am I
> wrong ?

The query timeout applies to JDBC positioning calls as well, including
next(), I think. It may not be what you need though.

Dag

Mime
View raw message