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 "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/08/06 18:56:14 UTC
[jira] Closed: (DERBY-1638) JUnit TestConfiguration class uses
engine code to determine JDBC level.
[ http://issues.apache.org/jira/browse/DERBY-1638?page=all ]
Daniel John Debrunner closed DERBY-1638.
----------------------------------------
Fix Version/s: 10.2.0.0
Resolution: Fixed
> JUnit TestConfiguration class uses engine code to determine JDBC level.
> -----------------------------------------------------------------------
>
> Key: DERBY-1638
> URL: http://issues.apache.org/jira/browse/DERBY-1638
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.2.0.0
>
> Attachments: derby1638_diff.txt
>
>
> TestConfiguration uses the org.apache.derby.iapi.services.info.JVMInfo to determine if JDBC 4 is supported. Ideally test code should not be calling engine private api code.
> Suggest two changes:
> 1) Determine JDBC level support from ability to load classes:
> E.g. JDBC2 - java.sql.Driver
> JDBC3 - java.sql.Driver AND java.sql.ParameterMetaData
> JDBC4 - java.sql.Driver AND java.sql.SQLXML
> JSR169 - java.sql.ParameterMetaData AND NOT java.sql.Driver
> 2) Move the supportsJDBC4() method from TestConfiguraiton to JDBC, since if the VM supports JDBC4 or not is
> not an attribute of a test configuration (and add other supportsJDBCX methods).
--
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