[
https://issues.apache.org/jira/browse/DERBY-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576603#comment-13576603
]
Rick Hillegas commented on DERBY-1184:
--------------------------------------
Hi Dag,
Yes, that's right. Now the typeName parameter is ignored as the javadoc
requires. The client and embedded drivers do the same thing: instead of
throwing an exception, the method is forwarded to
CallableStatement.registerOutParameter( int, int ). Over the past several
years, this method has had various behaviors on Derby depending on the driver:
1) Vacuous. Silently does nothing.
2) Throws an exception.
3) Forwards to another overload.
Now both drivers do (3).
Thanks,
-Rick
> '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
