Ignore a nil Or in Where, matching nil predicates - #401
Open
AshSgDe29071999 wants to merge 1 commit into
Open
Conversation
Where(nil) is a no-op, but a typed-nil Or (return nil from a helper
typed as sq.Or) is a non-nil interface and became WHERE (1=0).
Treat a nil Or like a nil predicate so optional filters do not invert
the query. An empty Or{} is unchanged.
See Masterminds#382
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
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.
Fixes #382
Where(nil)is documented as a no-op, but a helper typed assq.Orthat returnsnilis a typed-nil interface. That is not== nil, so it was compiled asWHERE (1=0)and inverted optional filters.An empty
Or{}is unchanged (1=0). The same ignore is applied on Update and Delete Where for consistency.