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] Commented: (DERBY-3041) Merge the separate JDBC 2.0 and JDBC 3.0 implementations in the ij code (Main/Main14 and utilMain/utilMain14)
Date Sun, 02 Sep 2007 16:09:19 GMT

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

Knut Anders Hatlen commented on DERBY-3041:

There's another workaround for JCC not supporting Connection.createStatement(int,int,int).
According to the code, SQLException or AbstractMethodError is to be expected, but when I tried
it with a small Java program, it worked perfectly fine. I tested it with JCC 2.4, which is
the lowest version supported by Derby, so I think it would be OK to remove that workaround
as well. In that case, utilMain.createStatement() could be removed entirely since it will
only forward the call to Connection.createStatement().

> 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:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: d3041-1.diff, d3041-1.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.

View raw message