Use StringBuilder in JdbcTemplate for batch updates #36032
Closed
+12
−6
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.
Description
As discussed in issue #36030, this PR refactors the exception handling logic within
JdbcTemplate.batchUpdate(String... sql).Currently, String concatenation is used inside a loop when constructing the error
message for a
BatchUpdateException. This PR replaces it withStringBuildertoavoid unnecessary temporary object allocation in the failure path.
Changes
StringBuilder: avoids unnecessary temporaryobject allocation for loop-based SQL accumulation.
Math.min(updateCounts.length, sql.length)to safelyhandle edge cases where JDBC drivers may return fewer update counts than the number
of SQL statements.
resulting error message format is identical to the previous implementation.
Verification
Verified by the existing CI test suite.