[
https://issues.apache.org/jira/browse/DERBY-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007124#comment-13007124
]
Lily Wei commented on DERBY-5134:
---------------------------------
Thanks Rick and Knut. How many other calls that require implementing named
parameters? Will it be for JDBC 4.1 or other JDBC version? From user
perspective, getObject(String,Class) is more visible than named parameters. I
agree once we have parameter name to parameter index, it should be pretty
straight forward to implement all of the getXXX(String) methods.
> 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
