[
https://issues.apache.org/jira/browse/DERBY-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756878#comment-13756878
]
ASF subversion and git services commented on DERBY-6324:
--------------------------------------------------------
Commit 1519785 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1519785 ]
DERBY-6324; DatabaseMetaData.getJDBCMinorVersion() should return 2 now that
we've implemented JDBC 4.2
Adding logic to JVMInfo to identify the supported JDBC level based on the
(currently supported) JVM versions, which then is used in the client and
embedded drivers.
Tests are changed to reflect this.
> 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
> Attachments: 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
