JdbcTemplate should store generated keys only if database driver supports it #31463
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.
Not every database supports
PreparedStatement#getGeneratedKeys()
, for example, SQLLitle does not, and calling this method throws an exception, it has been discussed here: xerial/sqlite-jdbc#996JdbcTemplate
callsPreparedStatement#getGeneratedKeys()
whether it's supported or not, and in the case of SQLLitle, it causes an exception.This PR changes the behavior of
JdbcTemplate
that it will callPreparedStatement#getGeneratedKeys()
only if the underlying driver supports it by querying:DatabaseMetaData#supportsGetGeneratedKeys()
.