db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6324) DatabaseMetaData.getJDBCMinorVersion() should return 2 now that we've implemented JDBC 4.2
Date Thu, 05 Sep 2013 18:52:51 GMT

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

Myrna van Lunteren resolved DERBY-6324.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.10.1.3

The nightly tests passed (almost) cleanly, so resolving this issue.
                
> DatabaseMetaData.getJDBCMinorVersion() should return 2 now that we've implemented JDBC
4.2
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6324
>                 URL: https://issues.apache.org/jira/browse/DERBY-6324
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.10.1.1
>            Reporter: Rick Hillegas
>            Assignee: Myrna van Lunteren
>             Fix For: 10.10.1.3
>
>         Attachments: DERBY-6324_1010.diff, DERBY-6324_2.diff, DERBY-6324.diff
>
>
> Now that the work on DERBY-6000 is done, DatabaseMetaData.getJDBCMinorVersion() should
return 2 rather than 1. The following script shows that we're still returning 1:
> connect 'jdbc:derby:memory:db;create=true';
> call syscs_util.syscs_register_tool( 'databaseMetaData', true );
> values getJDBCMajorVersion();
> values getJDBCMinorVersion();
> call syscs_util.syscs_register_tool( 'databaseMetaData', false );

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

Mime
View raw message