[
https://issues.apache.org/jira/browse/DERBY-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576293#comment-13576293
]
Dag H. Wanvik commented on DERBY-1184:
--------------------------------------
So, after your changes the method isn't vacuous as it was before this issue was
resolved? If so, I guess the net effect of your changes is to ignore the
typeName parameter, whereas before it thew an exception. Am i understanding
this correctly? Does this change make network and embedded clients diverge in
behavior on this?
> 'CallableStatement.registerOutParameter(int,int,String)' does nothing in
> client driver
> --------------------------------------------------------------------------------------
>
> Key: DERBY-1184
> URL: https://issues.apache.org/jira/browse/DERBY-1184
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Environment: Derby network client
> Reporter: Kristian Waagan
> Assignee: Bryan Pendleton
> Priority: Minor
> Fix For: 10.2.1.6
>
> Attachments: derby-1184-1a.diff, derby-1184-1a.stat,
> derby_1184_with_test.diff
>
>
> The method 'CallableStatement.registerOutParameter(int,int,String)' does
> nothing in the client driver. As stated in DERBY-447, the method throws a
> not-implemented exception in the embedded driver. The method should be
> changed to do this on the client side as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
