김준형 e06482ad51 Reject overlapping declared and generated key columns in SimpleJdbcInsert ...

When a column was declared via usingColumns() and also listed in
usingGeneratedKeyColumns(), TableMetaDataContext.reconcileColumnsToUse
accepted the declared list as-is: the generated key column was rendered
into the INSERT statement and counted against the parameter values,
even though the database is expected to generate its value.

Such an overlap is a configuration error, so it is now rejected at
compile time with an InvalidDataAccessApiUsageException naming the
offending columns in their declared spelling, consistent with the
existing validation in AbstractJdbcInsert.compile(). Matching is
case-insensitive, mirroring the normalization used for auto-discovered
columns; the auto-discovery path itself is unchanged and continues to
exclude generated key columns silently.

The tests cover the rejection, its message, a case-insensitive variant,
and the untouched non-overlapping declared path.

Closes gh-37014

Signed-off-by: junhyeong9812 <pickjog@gmail.com>

2026-09-07 10:34:38 +02:00

..

java/org/springframework/jdbc

Reject overlapping declared and generated key columns in SimpleJdbcInsert

2026-09-07 10:34:38 +02:00

kotlin/org/springframework/jdbc/core

Fix JdbcOperations Kotlin extensions

2025-11-19 15:55:00 +01:00

resources

Recognize error code 149 as deadlock loser (MySQL Galera)

2026-03-21 12:04:00 +01:00