This repository has been archived by the owner on Mar 30, 2022. It is now read-only.
Remove where clause grouping from RelationExtensions#collapse_wheres #424
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.
When a column is referenced in more than one where clause, the group_by and subsequent re-ordering of columns can cause the wrong bound values to be associated with columns. The columns are reordered, but the bound values are attached in their original order.
It looks like the current collapse_wheres in Squeel is based on the one from Active Record 3
I am unsure why the columns were grouped originally, but this now results in incorrect behavior under certain circumstances. You can see that in Active Record 4's version of this method, where clauses are no longer grouped.
My change removes the grouping and reordering.
With the original collapse_wheres, you can see the spec I have added failing:
Note that as the query was built, it is trying to use "long" as the cat's name instead of "Crookshanks".