feat(drive)!: allow to use range operators only in last where condition
#201
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
shumkov
requested changes
Jan 19, 2022
shumkov
approved these changes
Jan 19, 2022
shumkov
changed the title
in and startsWith only in last where conditionwhere condition
shumkov
changed the title
where conditionwhere condition
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.
Issue being fixed or feature implemented
Due to GroveDB technical limitations, we can allow using range operators (
in, 'startsWith',<,>,<=,>=) only for the last indexed property.What was done?
validateQueryHow Has This Been Tested?
Unit tests
Breaking Changes
Some existing queries won't be valid
Checklist:
For repository code-owners and collaborators only