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-2515) Network client does not retain the INOUT parameter value change for subsequent execution
Date Wed, 30 Mar 2011 12:59:05 GMT

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

Rick Hillegas commented on DERBY-2515:

Thanks for looking at the patch, Knut. Some answers to your questions follow:

1) No checking has been made to ensure that the Integer won't truncate silently when it is
stuffed into the Short. I can run some experiments to see what happens when you try to send
a large int across the network for use by a SMALLINT INOUT arg.

2) Cursor.getObject() can raise SqlException. But if it does that probably indicates a bug--it
is returning what java.sql.CallableStatement.getObject() is supposed to return. I could narrow
that catch down to just filter out SqlExceptions. StatementCallbackInterface.completeExecuteCall()
raises no errors and its callers perform no error handling other than to relay DisconnectExceptions
up the call stack.


> Network client does not retain the INOUT parameter value change for subsequent execution
> ----------------------------------------------------------------------------------------
>                 Key: DERBY-2515
>                 URL: https://issues.apache.org/jira/browse/DERBY-2515
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Priority: Minor
>              Labels: derby_triage10_8
>             Fix For:
>         Attachments: Test_2515.java, derby-2515-01-ac-copyINOUTreturnValues.diff
>  If I set a INOUT parameter to a value (say 12.3) and it gets 
> modified by the procedure to another value (say 45.6) then on 
> the next execution
>      of the same CallableStatement, embedded maintains the 
> current value (45.6), while network server reverts to the 
> former value (12.3).  
> This issue was found while converting the test lang/procedure.java.  See references to
this issue in the converted LangProcedureTest.java

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message