Allow grouping in querying #33
Merged
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
…he test itself is refactored to understand the new parsed query tree.
|
@mehcode ping |
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 overhauls the querying module to allow for grouping and fixes bugs where some OR querys were being treated as AND queries. Note that this changes the structure of the
Queryobject itself. Instead of being an iterable containing manyQuerySegments on an equal level, it is now a tree style structure that includesBinaryQuerySegments to link queries together. This could actually use a bit more work in the code organization and cleanup department, but all the features are implemented!a=b&(b=c;c=d)&!(e=f;g=h)works! 🎉