[
https://issues.apache.org/jira/browse/DERBY-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007021#comment-13007021
]
Rick Hillegas commented on DERBY-5134:
--------------------------------------
Note that the underlying problem is that the CallableStatement.getXXX(String)
methods are not implemented. Once they are implemented, implementing this
overload is trivial.
> CallableStatement.getObjet(string,class) returns JDBC method is not yet
> implemented exception
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-5134
> URL: https://issues.apache.org/jira/browse/DERBY-5134
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.7.1.1
> Environment: Windows 7
> Reporter: Lily Wei
> Labels: derby_triage10_8
>
> CallableStatement.getObjet(string,class) returns JDBC method is not yet
> implemented exception.
> Please refer to http://wiki.apache.org/db-derby/JDBCSupport for more
> information.
> i.e. The following code is not supported:
> CallableStatement.getObject( colID, candidate ); //String colID, Class
> candidate
> (You may find the similar code in
> org.apache.derbyTesting.functionTests.tests.jdbc4.CallableStatementTest)
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
