db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1698) Add more tests for Statement.setQueryTimeout method
Date Fri, 25 Aug 2006 04:51:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1698?page=comments#action_12430388 ] 
V.Narayanan commented on DERBY-1698:

jdbcapi/SetQueryTimeoutTest.java was earlier being limited by DERBY-694 and is no more. Please
find DERBY-705 related to this

> Add more tests for Statement.setQueryTimeout method
> ---------------------------------------------------
>                 Key: DERBY-1698
>                 URL: http://issues.apache.org/jira/browse/DERBY-1698
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions:,
>            Reporter: Deepa Remesh
>         Assigned To: Deepa Remesh
>            Priority: Minor
>         Attachments: derby-1698.diff, derby-1698.status
> Currently, the following checks work as expected but it would be good to add them to
regression tests:
> * Add tests to check query timeout value is used by executeUpdate method. Existing test
tests calls to execute and executeQuery. The following mail mentions query timeout limit should
be applied for all  executeXXX methods. http://www.nabble.com/Statement.setQueryTimeout-tf94429.html#a258410

> * Add tests for Statement and CallableStatement class. Existing test tests this method
with PreparedStatement only. I found a difference in behaviour with client driver when using
Statement class (DERBY-1692). So it may be good to add some tests for each statement class.

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


View raw message