db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ali Demir (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-31) Statement.setQueryTimeout() support.
Date Fri, 17 Dec 2004 17:40:15 GMT
     [ http://nagoya.apache.org/jira/browse/DERBY-31?page=comments#action_56831 ]
     
Ali Demir commented on DERBY-31:
--------------------------------

When a time out is set to n millis, and if the query takes n+m millis, then caller would expect
that time out occurs around n millis and not wait until n+m. Also, when the timeout occurs,
the processing of the query should have been stopped and there should not be any locks held
after timeout. Therefore, a simple solution that simply checks how long the query processing
is taking is not enough. The internals of the system need to know that it should stop the
query and release any locks held by it when the timeout occurs.

> Statement.setQueryTimeout() support.
> ------------------------------------
>
>          Key: DERBY-31
>          URL: http://nagoya.apache.org/jira/browse/DERBY-31
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>  Environment: ALL
>     Reporter: Ali Demir

>
> Calling Statement.setQueryTimeout() throws exception saying that function is not supported.
This is an important JDBC feature and is limiting our options to use Derby with our JDBC code.
Implementing this JDBC function would make Derby much easier to adopt.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message