Update .pluck documentation on uniq #20708
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
This is to show users that they can chain `.uniq` and `.pluck` to get the `DISTINCT column` result. They don't have to do `DISTINCT column` themselves.
|
@sikachu 👍 Thank you! <3 |
zzak
pushed a commit
that referenced
this pull request
Jun 26, 2015
Update .pluck documentation on uniq
|
As I remember uniq is not very welcome on relation. We'd better use |
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.
This is to show users that they can chain
.uniqand.pluckto get theDISTINCT columnresult. They don't have to doDISTINCT columnthemselves.I'm submitting this as a PR as this changes the way we represent this method to users. I think it's fine, as we already show that this method supports SQL statement below.