db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1692) Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object
Date Wed, 16 Aug 2006 18:15:16 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1692?page=comments#action_12428454 ] 
            
Deepa Remesh commented on DERBY-1692:
-------------------------------------

Thanks Knut Anders for fixing this bug so quickly. I verified the patch solves this issue.
And thanks for adding the new test covering all statement classes. My +1 to commit this patch
(if derbyall ran okay).

> 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
>         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

        

Mime
View raw message