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 "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/08/15 21:20:14 UTC
[jira] Assigned: (DERBY-1698) Add more tests for
Statement.setQueryTimeout method
[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ]
Deepa Remesh reassigned DERBY-1698:
-----------------------------------
Assignee: Deepa Remesh
> 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: 10.2.0.0, 10.3.0.0
> Reporter: Deepa Remesh
> Assigned To: Deepa Remesh
> Priority: Minor
>
> 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