[ http://issues.apache.org/jira/browse/DERBY-1184?page=comments#action_12373442 ]
Kristian Waagan commented on DERBY-1184: ---------------------------------------- Yes, a test should be added, but since the existing test was canon based test, I did not find the time to add a test and update the canons. This is not my itch at the moment, I stumbled over this when working on a JDBC4 feature. If it is of interest, I can add a test for this in the jdbc4/CallableStatementTest, but it would then only be run under JDK 1.6. If the missing test is a blocker, I suggest the patch is put on hold until someone else find the time to write/update the test. I created the quick patch because I found the bug quite ugly; a method pretending everything is okay, when it actually does nothing... > '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
