db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver
Date Fri, 07 Apr 2006 15:14:25 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1184?page=comments#action_12373649 ] 

Kristian Waagan commented on DERBY-1184:

Code changes are okay and works as expected, but the test has become out of synch with the
SQL states.  In revision 392060, the SQL state "0AX01" was replaced by "0A000". I suggest
a committer takes care of this simple change in the test derbynet/callable.java.

When the test is updated, the issue can be closed.

> '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:
>  Environment: Derby network client
>     Reporter: Kristian Waagan
>     Assignee: Bryan Pendleton
>     Priority: Minor
>      Fix For:
>  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 contact one of the administrators:
For more information on JIRA, see:

View raw message