Issue/3460

[thjanssen]

Fix handling of position INOUT parameters when extracting output parameters (issue 3460)

• [x] You have read the Spring Data contribution guidelines.
• [x] You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• [x] You submit test cases (unit or integration tests) that back your changes.
• [x] You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

Added position information to ProcedureParameter class, set it in StoredProcedureAttributeSource.extractOutputParametersFrom(...), and use that position in StoredProcedureJpaQuery.extractOutputParameterValue to get the result value. This change is based on the assumption that NamedStoredProcedureQuery.parameters() returns the parameters in the correct order. As far as I understand the rest of the code, it already makes this assumption when using positional parameters.

[pivotal-cla]

@thjanssen Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[pivotal-cla]

@thjanssen Thank you for signing the Contributor License Agreement!

[thjanssen]

When this is fixed, do you think you could backport it to version 3.2.x?

[christophstrobl]

I intend to back port the fix if things work out as expected.

[christophstrobl]

Thank you @thjanssen - merged to main development line and back ported to 3.2.x.