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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2013/08/29 18:22:57 UTC
[jira] [Assigned] (DERBY-6324)
DatabaseMetaData.getJDBCMinorVersion() should return 2 now that we've
implemented JDBC 4.2
[ https://issues.apache.org/jira/browse/DERBY-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-6324:
-----------------------------------------
Assignee: Myrna van Lunteren
> 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
>
> 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