Rails queries acts like arrays, thus .uniq
produces the same result as .distinct
, but
.distinct
is sql query method
.uniq
is array method
Note: In Rails 5+ Relation#uniq
is deprecated and recommended to use Relation#distinct
instead.
See http://edgeguides.rubyonrails.org/5_0_release_notes.html#active-record-deprecations
Hint:
Using .includes
before calling .uniq/.distinct
can slow or speed up your app, because
uniq
won't spawn additional sql query
distinct
will do
But both results will be the same
Example:
users = User.includes(:posts)
puts users
# First sql query for includes
users.uniq
# No sql query! (here you speed up you app)
users.distinct
# Second distinct sql query! (here you slow down your app)
This can be useful to make performant application
Hint:
Same works for
.size
vs .count
;
present?
vs .exists?
map
vs pluck
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…