[DERBY-2515] Network client does not retain the INOUT parameter value change for subsequent execution

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.5.3.2, 10.6.2.4, 10.7.1.4, 10.8.1.2
• Component/s: Network Client
• Labels: derby_triage10_8
• Urgency: Urgent
• Issue & fix info: High Value Fix, Newcomer, Repro attached
• Bug behavior facts: Embedded/Client difference, Wrong query result
• Assignee: Richard N. Hillegas
• Reporter: Katherine Marsden
• Created: 02/Apr/07 23:26
• Updated: 17/Jun/13 09:19
• Resolved: 21/Mar/12 13:02

Description

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

Issue Links

• depends upon: DERBY-5162 CLOB INOUT arg set to NULL by procedure does not preserve NULL value when re-invoked
• is related to: DERBY-2461 Convert lang/procedure.java to junit
• is required by: DERBY-5654 10.5 Backport issue (2012)