db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1638) JUnit TestConfiguration class uses engine code to determine JDBC level.
Date Thu, 03 Aug 2006 05:33:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1638?page=all ]

Daniel John Debrunner updated DERBY-1638:

    Attachment: derby1638_diff.txt

Patch that makes described changes, adding these methods


Might consider changing the methods to be *is* instead of *supports* (e.g isJDBC4()) since
they are describing
that the environment is JDBC 4, not what any client may support.

Then new (yet to be added) methods called supportsJDBC4() might make sense in TestConfiguraiton
or maybe JDBCClient to indicate that the client under test is running at a different level,
e.g. for the ability to support testing the old 10.1 driver in jdk16 against the new 10.2

> 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
>         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


View raw message