On Nov 14, 2014, at 4:05 PM, Sunny Juneja <jr.su...@gmail.com> wrote:
> Hey, I ran into this problem fairly recently. I needed to get a large number
> of records and search them over and over again on different attributes. I
> found myself writing code that looked a lot like this.
>
> records = Model.where(...)
>
> records.select { |r| r.attribute1 == attribute1 && r.attribute2 == attribute2
> && ... }
>
> Although this is a simple case, I found myself rewriting this over and over
> again.
>
> Is there anything equivalent that might fit the form
>
> records = Model.where(...)
> records.find_in_relation(attribute1: attribute1, attribute2: attribute2,
> attribute3, ...)
>
> Was just wondering if there was a place for such syntactical sugar or a
> desire to add some. If there is too simple a change to warrant, I understand.
If attribute1, attribute2, etc are database columns then I think `where` is the
same as your `find_in_relation`…
records = Model.where(...)
records.where(attribute1: attribute1, attribute2: attribute2, attribute3, …)
Can you explain further what `find_in_relation` is intended to do differently?
—Matt Jones
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
