Fix Ransack redundant left join statements #1612
Draft
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.
Fix for Redundant Left Join Issue
Problem:
Ransack was generating redundant LEFT OUTER JOIN statements when INNER JOINs to the same table already existed in the relation.
Root cause:
The
@joined_tables
hash inJoinDependency
was only tracking OuterJoin types, not InnerJoins, causing Ransack to create new LEFT OUTER JOINs to tables that were already joined with INNER JOINs.Solution:
table_aliases_for
method to track ALL join types in@joined_tables
, not just OuterJoinsChanges:
lib/polyamorous/activerecord/join_dependency.rb
: Removed condition that only tracked OuterJoins in@joined_tables
spec/ransack/adapters/active_record/redundant_joins_spec.rb
: Added comprehensive tests to prevent regressionBefore Fix:
After Fix:
The fix ensures that when a relation already has INNER JOINs to certain tables, Ransack will reuse those tables instead of creating redundant LEFT OUTER JOINs.
Fixes #1433
Fixes #1433
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.