db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-2438) Remove JDBC20Translation and JDBC30Translation classes
Date Sat, 01 Jun 2013 11:11:21 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen updated DERBY-2438:

    Attachment: jdbc30.diff

Now that the base level is JDBC 4.0, we can use the ParameterMetaData constants directly and
remove them from JDBC30Translation. Some constants that are not actually JDBC constants have
sneaked into JDBC30Translation over time, and they are still needed.

Also, most of the constants in JDBC40Translation can be replaced with references to the actual
JDBC constants. Only the JDBC 4.2 constant Types.REF_CURSOR still needs to be in JDBC40Translation.

The attached jdbc30.diff patch eliminates the JDBC30Translation interface by using ParameterMetaData
constants directly, and moving the remaining non-JDBC constants over to JDBC40Translation.

The patch also replaces most constants in JDBC40Translation with their corresponding constants
in DatabaseMetaData or Types. And it removes the JDBC40TranslationTest class, since all the
constants tested in that class are removed by the patch.

All tests ran cleanly with the patch. Tested on both Java 6 and Java 8.
> Remove JDBC20Translation and JDBC30Translation classes
> ------------------------------------------------------
>                 Key: DERBY-2438
>                 URL: https://issues.apache.org/jira/browse/DERBY-2438
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>            Reporter: Daniel John Debrunner
>         Attachments: jdbc20.diff, jdbc20.stat, jdbc30.diff
> Now that JDBC 3.0/JSR 169 is the base level these constants can be used directly from
the java.sql classes.

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

View raw message