fix multi filtering for gorm 1.25.6 #5
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
survivorbat
approved these changes
Jan 29, 2024
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.
gorm 1.25.6 update changed the way a where clause with multiple expressions is represented.
I the previous version it was stored as an array of multiple clause.Eq expressions.
In 1.25.6 it changed to be an array of clause.AndConditions expressions which in turn can contain an array clause.Eq expressions or other clause.AndConditions expressions.
This broke the test case regarding the "multi filter".
A recursive function was added to fix this issue, going recursively into the clause.AndConditions.