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] Commented: (DERBY-3041) Merge the separate JDBC 2.0 and JDBC 3.0 implementations in the ij code (Main/Main14 and utilMain/utilMain14)
Date Mon, 19 Nov 2007 17:40:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543622
] 

Rick Hillegas commented on DERBY-3041:
--------------------------------------

Is it worth porting this set of patches to 10.3?

> Merge the separate JDBC 2.0 and JDBC 3.0 implementations in the ij code (Main/Main14
and utilMain/utilMain14)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3041
>                 URL: https://issues.apache.org/jira/browse/DERBY-3041
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 10.4.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: d3041-1.diff, d3041-1.stat, d3041-2.diff, d3041-2.stat
>
>
> The classes utilMain and utilMain14 contain utility methods for manipulating the holdability
of a connection or a statement. There is one implementation for JDBC 2.0 JVMs and one implementation
for JDBC 3.0 JVMs. Since Derby now only supports JVMs which support JDBC 3.0 (or JSR-169 which
is a subset of JDBC 3.0), we could move code from utilMain14 to utilMain and delete utilMain14.
The class Main14 behaves identically to the class Main, except that it returns utilMain14
instances, so once the utilMain14 class is removed, Main14 can be removed as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message