Hi Dirk,
Yes, Derby does support Statement.setQueryTimeout(), at least as
verified by the Derby regression test
org.apache.derbyTesting.functionTests.tests.lang.SetQueryTimeoutTest.
That's a good defense if you suspect in advance that your queries may
ramble on. It leaves the lingering issue of how to cancel a runaway
query that you (or someone else) didn't limit before the query started.
Hope this helps,
-Rick
Dirk Flachbart wrote:
Doesn't Derby support Statement.setQueryTimeout() ?
Dirk
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> wrote:
A rollback doesn't "cancel" a query. Meaning that you can't stop the query
until it completes.
The rollback will reverse the results of a transaction after the SQL
statement completes. A query is unaffected because its not a SQL statement
that changes the database. (query == SELECT, other statements UPDATE,DELETE,
INSERT, etc ... do change the data.)
So if you start a query, there isn't a way to have some sort of query
timeout or call to prematurely end the query. (Perhaps you need to consider
threading your app...)
HTH
-Mike
-----Original Message-----
From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 9:09 PM
To: Derby Discussion
Subject: Re: cancel a running query?
Rick Hillegas <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> writes:
conn.rollback();
Doesn't the rollback block on synchronizion on the connection?
Dag
