Fix SimpleJdbcCall
named parameter binding for Sybase ASE
#30231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes an issue with Sybase named parameter binding in the code. The
namedParamBindingToUse
method has been updated to properly handle named parameters in Sybase stored procedures. Prior to this fix, the method may not have returned the correct named parameter for a given parameter name, causing issues with stored procedure execution.This fix is necessary to ensure proper execution of Sybase stored procedures that use named parameters.
When working with Sybase ASE stored procedures, parameters should be supplied in the order of their create procedure statement, unless they are supplied in the form
@<parameter> = <value>
, in which case they can be supplied in any order. For more information, see the Sybase ASE documentation: https://help.sap.com/docs/SAP_ASE/b65d6a040c4a4709afd93068071b2a76/aa8728babc2b101491a4f578b9082925.html?locale=en-US