Fix merging conditions on same column #11
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
Merging conditions on the same column no longer maintain both conditions, and will be consistently replaced by the latter condition. See: https://edgeguides.rubyonrails.org/7_0_release_notes.html#active-record-notable-changes Basically Relation#merge behaves almost like Hash#merge. If you want both conditions are remained, use Relation#and instead in Rails 6.1. See: rails/rails#40944 (comment)
The approach in previous commit was requiring that relation passed to #and should be structurally compatible. In this solution the returned query is the result of just chain all filters to current scope.
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.
Merging conditions on the same column no longer maintain both conditions, and will be consistently replaced by the latter condition.