db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1059) call to stored procedure with out params fails in embedded driver
Date Fri, 10 Mar 2006 08:34:44 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1059?page=comments#action_12369822 ] 

Anurag Shekhar commented on DERBY-1059:
---------------------------------------

CallableStatement40 and PreparedStatement40 needs to extend their respective 30 classes. 
If we have a new common parent class will have to implement all prepared stament methods (including

the older methods) in addition to that PreparedStatement  40 and CallableStatement40 will
have to redo 
all the steps to create prepared/callable statment. I am assuming that you are not suggesting
me to 
change the inheritance structure of pre jdbc4.0 drivers. 

I will add the javadoc for setBlob and setClob. I have removed this by mistake thanks for
pointing out.

anurag


> call to stored procedure with out params fails in embedded driver
> -----------------------------------------------------------------
>
>          Key: DERBY-1059
>          URL: http://issues.apache.org/jira/browse/DERBY-1059
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC
>     Versions: 10.2.0.0
>     Reporter: Anurag Shekhar
>     Assignee: Anurag Shekhar
>  Attachments: derby-1059.diff, derby-1059_2.diff
>
> org.apache.derby.impl.jdbc.EmbeddedCallableStatement40 and org.apache.derby.client.am.CallableStatement40
are instantiating Preparewdstament in 
> constructor. Becasue of this call to stored procedure with out param fails.
> Instantiatiation of prepared was done to share the common method in prepared statement
and callbale statement. But this aporach causes another issue of creating two instance of
statement (one by calling super () and another by instantiating prepared statement). 
> I can think of two solution of this problem 
> 1. Create another class which handles the common methods in PrepardStatement40 and CallableStatement40
classes.
> 2. Duplicate the common method in both classes. 
> I feel 1st one is better. It will will be easier to fix any issue in the common methods
and chance to miss to fix in one of the classes will be eliminated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message