[ http://issues.apache.org/jira/browse/DERBY-1184?page=all ]
Kristian Waagan updated DERBY-1184:
-----------------------------------
Attachment: derby-1184-1a.diff
derby-1184-1a.stat
'derby-1184-1a.diff' changes the method
CallableStatement.registerOutParameter(int,int,String) to throw a
not-implemented exception. It was doing nothing before (no actions taken, no
exceptions thrown except for the case where the method was called on a closed
CallableStatement).
derbyall is running. I will report tomorrow if there are problems, but I don't
expect that to be the case since the method is probably not used in any tests.
This patch fixes one of the differences between embedded and client driver
reported in DERBY-477.
> 'CallableStatement.registerOutParameter(int,int,String)' does nothing in
> client driver
> --------------------------------------------------------------------------------------
>
> Key: DERBY-1184
> URL: http://issues.apache.org/jira/browse/DERBY-1184
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> Environment: Derby network client
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-1184-1a.diff, derby-1184-1a.stat
>
> 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 contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
