Support negated filters on one-to-one and many-to-one Relationships #26
Conversation
This file contains hidden or 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
camuthig
force-pushed
the
support-single-forward-negation-filter
branch
from
2930936 to
ef61476
Compare
camuthig
changed the title
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 makes it possible to have a one-to-one and many-to-one
Relationshipwith bothmultipleset toFalseand execute negated queries on it. This sort of relationship does not need to create aWHERE NOT EXISTsubquery, and by setting them2mvariable the ORM will generate the correct query for us.This does not solve the larger issue for a one-to-many or many-to-many relationship and negated queries.