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 <m....@gmail.com> on 2013/08/29 00:29:21 UTC

support for JDBC 4.2 complete?

Hi,

With DERBY-6000 support was added for JDBC 4.2 (by Rick).
But I tried DatabaseMetaData.getJDBCMinorVersion(), which returned 1, on a
trunk (10.11 alpha at 1517615M).

Was updating the value this method returns (to '2', I assume) forgotten or
is there more work to do?

Myrna

Re: support for JDBC 4.2 complete?

Posted by Rick Hillegas <ri...@oracle.com>.

On 8/28/13 3:29 PM, Myrna van Lunteren wrote:
> Hi,
>
> With DERBY-6000 support was added for JDBC 4.2 (by Rick).
> But I tried DatabaseMetaData.getJDBCMinorVersion(), which returned 1, 
> on a trunk (10.11 alpha at 1517615M).
>
> Was updating the value this method returns (to '2', I assume) 
> forgotten or is there more work to do?
>
> Myrna
>
>
Thanks for noticing this, Myrna. I've logged DERBY-6324 to track this 
defect. The return value of that method should have been updated as part 
of declaring victory on DERBY-6000.

Thanks,
-Rick