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] [Created] (DERBY-5874) Remove JDBC 3 constants from client.am.Statement
Date Mon, 23 Jul 2012 12:58:34 GMT
Knut Anders Hatlen created DERBY-5874:
-----------------------------------------

             Summary: Remove JDBC 3 constants from client.am.Statement
                 Key: DERBY-5874
                 URL: https://issues.apache.org/jira/browse/DERBY-5874
             Project: Derby
          Issue Type: Improvement
          Components: JDBC
    Affects Versions: 10.10.0.0
            Reporter: Knut Anders Hatlen
            Assignee: Knut Anders Hatlen
            Priority: Trivial


org.apache.derby.client.am.Statement defines three constants, CLOSE_CURRENT_RESULT, KEEP_CURRENT_RESULT
and CLOSE_ALL_RESULTS, that are also defined in java.sql.Statement. Since client.am.Statement
implements java.sql.Statement, we could remove those constants and let it inherit them instead.
The only reason why these constants are defined in client.am.Statement, is to make the client
compile on JDKs predating JDBC 3 (that is, Java 1.3 and earlier). Since we don't support those
JDKs anymore, the constants can be removed now.

--
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

        

Mime
View raw message