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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2013/06/13 23:19:20 UTC
[jira] [Closed] (DERBY-6261) test getCurConnJdbc20.sql is no longer
useful and can be removed
[ https://issues.apache.org/jira/browse/DERBY-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-6261.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.11.0.0
> test getCurConnJdbc20.sql is no longer useful and can be removed
> ----------------------------------------------------------------
>
> Key: DERBY-6261
> URL: https://issues.apache.org/jira/browse/DERBY-6261
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.11.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Trivial
> Fix For: 10.11.0.0
>
>
> The old harness style test jdbcapi/getCurConnJdbc20.sql is the last test remaining in the jdbc20 suite.
> It runs with jdk12test=true, meaning with any jvm higher than 1.1.
> It creates a table, creates a procedure and executes it, then drops the table and procedure.
> The comment before running the function says:
> -- now lets try a variety of errors
> However, the function is util.Jdbc20Test.newToJdbc20Method, but all this does is:
> Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
> ResultSet.CONCUR_READ_ONLY);
> I don't see this doing anything more useful.
> Perhaps more interesting things were planned but never implemented, this type of statement is also created and tested in jdbcapi.ResultSetJdbc30Test, and we don't support anything older than 1.6 now anymore, so this test can just go.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira