[
https://issues.apache.org/jira/browse/DERBY-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2515:
---------------------------------
Attachment: Test_2515.java
Attaching Test_2515.java, a test case which shows this behavior. The embedded
and network drivers both reset purely OUT args the same way. INOUT args are
treated differently: the embedded driver does not touch the last value returned
but the client driver resets the INOUT arg to the last value set by its
setXXX() method.
> 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: 10.3.1.4
> Reporter: Kathey Marsden
> Priority: Minor
> Labels: derby_triage10_8
> Attachments: Test_2515.java
>
>
> 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
