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] Updated: (DERBY-1059) call to stored procedure with out params fails in embedded driver
Date Mon, 13 Mar 2006 21:35:41 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1059?page=all ]

Anurag Shekhar updated DERBY-1059:

    Attachment: derby-1059_2.diff

Move all the implemented methods of PreparedStatement40 and EmbedPreparedStatement40 to the
base class PreparedStatement and EmbedPreparedStatement.

Removed the instantiation of PreparedStatement40 and EmbedPreparedStatement40 from CallableStement40
and EmbedCallableStatement40

The unimplemented methods in CallableStatement inherited from java.sql.PreparedStement throws
NOT_IMPLEMENTED without calling respective PreparedStatement methods.

derbyall will jdk1.4.2 runs with 7 failure but they are related to i18n. 

jdbcapi/parameterMapping.java still fails with jdk1.6 but now the failure is due to exception
changed in 819. I am opening a new jira id to fix all message
related failure in jdk1.6

> 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:
>     Reporter: Anurag Shekhar
>     Assignee: Anurag Shekhar
>  Attachments: derby-1059.diff, derby-1059_2.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
> 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:
For more information on JIRA, see:

View raw message