[
https://issues.apache.org/jira/browse/DERBY-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2515:
----------------------------------
Affects Version/s: (was: 10.5.3.0)
10.3.1.4
Fix Version/s: 10.7.1.4
10.6.2.3
10.5.3.2
Assignee: Rick Hillegas (was: Kathey Marsden)
Reassigning to Rick and resolving. Also restoring the affects version. This was
accidentally changed with the bulk reopen. I had intended to add 10.5 as an
affects version but unfortunately that replaced what was there.
> 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
> Assignee: Rick Hillegas
> Priority: Minor
> Labels: derby_triage10_8
> Fix For: 10.5.3.2, 10.6.2.3, 10.7.1.4, 10.8.1.2
>
> Attachments: Test_2515.java,
> derby-2515-01-ac-copyINOUTreturnValues.diff,
> derby-2515-02-aa-polishCatchBlock.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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
