db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver
Date Mon, 11 Feb 2013 20:45:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576101#comment-13576101

Rick Hillegas commented on DERBY-1184:

Work on DERBY-6000 will undo work done on this issue. I am re-plumbing these methods so that
they forward to overloads which don't have the typeName parameter. Derby does not need the
type name in order to correctly dispatch these methods for UDT types. Since at least JDBC
3.0, the javadoc for these methods has said the following:

"A JDBC driver that does not need the type code and type name information may ignore it. To
be portable, however, applications should always provide these values for user-defined and
REF parameters. Although it is intended for user-defined and REF parameters, this method may
be used to register a parameter of any JDBC type. If the parameter does not have a user-defined
or REF type, the typeName parameter is ignored."
> '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:
>         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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message