Fix GRDB 5 regression with indexes on expressions #841
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request fixes #840, and the
Database.indexes(on:)method.Since its introduction,
Database.indexes(on:)had a bug which would make it crash with indexes on expressions.Now
Database.indexes(on:)no longer crashes, and just excludes such indexes from its result.It happens that this bug has introduced regressions in GRDB 5, which would crash when running some query interface requests on tables indexed on an expression. The reason in that GRDB 5 performs a more precise analysis of requests in order to optimize the generated SQL or detect misuses, and querying indexes is part of this analysis.