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] Updated: (DERBY-1698) Add more tests for Statement.setQueryTimeout method
Date Thu, 24 Aug 2006 06:49:47 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1698?page=all ]

Deepa Remesh updated DERBY-1698:

    Attachment: derby-1698.diff

Attaching a patch 'derby-1698.diff' which adds an additional test to jdbcapi/SetQueryTimeoutTest.java.
This patch adds a test for executeUpdate method call. Other tests for Statement and CallableStatement
class have been already added by Knut Anders. 

With this patch, I ran the test jdbcapi/SetQueryTimeoutTest.java with embedded and client
framework. It is excluded in JCC framework. 

This is a small patch which modifies only tests. Please take a look and commit if okay. Thanks.

> 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