Add support for specifying distinct columns in result queries #1594
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.
Addresses the issue where users could only use
distinct: true
to generateSELECT DISTINCT
on all columns, with no way to specify which specific columns should be included in the DISTINCT clause.What's Changed
Previously, users were limited to:
Now users can specify exactly which columns to use in the DISTINCT clause:
Implementation Details
lib/ransack/adapters/active_record/context.rb
to handle various distinct option typesdistinct: true
usage continues to work unchangedfalse
,nil
, empty arraysdistinct(*columns)
methodBenefits
This eliminates the need for workarounds that users previously had to employ:
Testing
Added comprehensive test coverage including:
Documentation
Updated the "Problem with DISTINCT selects" section in the documentation with examples and a complete reference of supported option types.
Fixes the issue where users needed to work around distinct limitations with manual column selection or alternative approaches like grouping.
Fixes #1533
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.