chore: mitigate possible future sqlite driver problems #4200
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.
Overview
Just to be on the safer side, if https://github.com/xerial/sqlite-jdbc/releases/tag/3.43.0.0 is embedded again into Spigot / CB / Paper.
Checks if Statement#getGeneratedKeys is supported by the driver otherwise falls back on sqlite drivers using the RETURN statement on inserts. When using MySQL and getGeneratedKeys is not supported, well - that's a whole other story (but that's a very unlikely event).
Tested using latest paper and paper build 207 with mysql and sqlite.
Submitter Checklist