db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5868) Move java.sql.Wrapper implementations to base classes on the client
Date Sat, 21 Jul 2012 08:21:35 GMT

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

Knut Anders Hatlen resolved DERBY-5868.

          Resolution: Fixed
       Fix Version/s:
    Issue & fix info:   (was: Patch Available)

Committed revision 1364042.
> Move java.sql.Wrapper implementations to base classes on the client
> -------------------------------------------------------------------
>                 Key: DERBY-5868
>                 URL: https://issues.apache.org/jira/browse/DERBY-5868
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>             Fix For:
>         Attachments: derby-5868-1a.patch
> The client classes that implement java.sql.Wrapper, implement the interface in the leaf
classes instead of the base classes. This is because unwrap() has a generic signature, so
it could not be in the base classes as long as they had to be compatible with Java 1.4.
> For example, in the statement class hierarchy, we implement unwrap() in Statement40,
PreparedStatement40 and CallableStatement40. Now that we compile the client with source level
1.5, we can move the unwrap() method to the Statement class and eliminate the duplication.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message