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] [Updated] (DERBY-6324) DatabaseMetaData.getJDBCMinorVersion() should return 2 now that we've implemented JDBC 4.2
Date Mon, 17 Feb 2014 21:46:21 GMT

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

Myrna van Lunteren updated DERBY-6324:
--------------------------------------

    Labels: derby_backport_reject_10_8 derby_backport_reject_10_9  (was: backport_reject_10.8)

> 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
>              Labels: derby_backport_reject_10_8, derby_backport_reject_10_9
>             Fix For: 10.10.1.4, 10.11.0.0
>
>         Attachments: DERBY-6324.diff, DERBY-6324_1010.diff, DERBY-6324_2.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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message