PhilCope <[EMAIL PROTECTED]> 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
