db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-6324) DatabaseMetaData.getJDBCMinorVersion() should return 2 now that we've implemented JDBC 4.2
Date Thu, 29 Aug 2013 12:28:53 GMT
Rick Hillegas created DERBY-6324:
------------------------------------

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


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