fix!: EXPOSED-269 Incompatible with sqlite-jdbc 3.45.0.0 #2030
+11
−17
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.
sqlite-jdbc 3.45.0.0 reintroduced improved support for
Statement#getGeneratedKeys()
, but the implementation is different from the previous implementation and does not work with Exposed. This is a temporary workaround to fix the crash caused by that until we figure out how we're supposed to use sqlite-jdbc 3.45.0.0+ with Exposed.To be investigated (YouTrack issue):
The problem is that a newly-introduced function
Statement#updateGeneratedKeys()
in sqlite-jdbc, which sets the value of the ResultSet, is not invoked whenexecuteBatch()
is used, but only withexecuteUpdate()
. This means that something probably has to be changed in the following function in InsertStatement.kt in Exposed to accommodate this new behaviour: