[
https://issues.apache.org/jira/browse/DERBY-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-5877.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
Issue & fix info: (was: Patch Available)
Committed revision 1365465.
> Prune the brokered class tree
> -----------------------------
>
> Key: DERBY-5877
> URL: https://issues.apache.org/jira/browse/DERBY-5877
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.10.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.10.0.0
>
> Attachments: d5877-1a.diff
>
>
> The brokered class tree still separates between the JDBC 2.0 functionality
> and JDBC 3.0. This leads to unnecessarily many levels of classes (for
> example, BrokeredPreparedStatement -> BrokeredPreparedStatement30 ->
> BrokeredStatement40). Another consequence is that BrokeredCallableStatement30
> and BrokeredPreparedStatement30 don't have a common base class that could
> hold shared JDBC 3.0 methods (their common base class is
> BrokeredPreparedStatement, which is JDBC 2.0), and therefore new JDBC 3.0
> PreparedStatement methods are duplicated in the two classes.
> We should fold the JDBC 3.0 classes into the JDBC 2.0 classes so that we can
> reduce the number of classes and the duplication of code in the brokered
> statement sub-tree.
--
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
