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] [Updated] (DERBY-2515) Network client does not retain the INOUT parameter value change for subsequent execution
Date Tue, 29 Mar 2011 14:17:06 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-2515:

    Attachment: derby-2515-01-ac-copyINOUTreturnValues.diff

Attaching derby-2515-01-ac-copyINOUTreturnValues.diff. This patch fixes the bug by copying
output values to the corresponding input array in the network driver.

The tests passed cleanly for me except for known Heisenbugs and a new failure in ProcedureTest
introduced by this patch. The new test case in ProcedureTest discloses DERBY-5162. Once that
bug is fixed, ProcedureTest should run cleanly too.

Touches the following files:


M      java/client/org/apache/derby/client/am/CallableStatement.java

In the network driver, input args and output args are maintained in two separate arrays. This
patch copies the output values of INOUT args to the corresponding slots in the input array.


M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/ProcedureTest.java

Adds a test case to verify that INOUT values are preserved across invocations for all datatypes.

> 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
>         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