You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/08/16 22:52:17 UTC
[jira] Resolved: (DERBY-1692) Client driver does not use the query
timeout value set using Statement.setQueryTimeout() for subsequent
executions using the same statement object
[ http://issues.apache.org/jira/browse/DERBY-1692?page=all ]
Knut Anders Hatlen resolved DERBY-1692.
---------------------------------------
Fix Version/s: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks Deepa! Derbyall passed and I committed the patches into trunk with revision 432029.
I have marked the issue as fixed in 10.2 although the fix hasn't been merged to the 10.2 branch yet. I assume it will be part of Rick's mega-merge. (Still a little confused after the vacation, so I might have misunderstood how this should be handled.)
> Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1692
> URL: http://issues.apache.org/jira/browse/DERBY-1692
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.2.0.0, 10.3.0.0
> Reporter: Deepa Remesh
> Assigned To: Knut Anders Hatlen
> Fix For: 10.2.0.0
>
> Attachments: derby-1692-tests.diff, derby-1692-tests.stat, derby-1692.diff, TestQueryTimeout.java
>
>
> I will attach a repro with more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira