Gotcha. In this case, since calls to Model.last(n) is inherently inefficient (loading everything and placing a limit), it's good to keep it till the end of the chain.
On Fri, Jul 19, 2013 at 11:55 AM, Tejas Dinkar <[email protected]>wrote: > On Jul-19-2013, at 8:08 PM, Mohamed Wael Khobalatte < > [email protected]> wrote: > > Because you won't need to run a query on one element? > > > I think the question is more about Model.last(5) or Model.first(5) > > These return arrays when they could return a relation. > -- > Tejas Dinkar > http://www.nilenso.com > Nilenso Software (formerly C42 Engineering) > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Mohamed Wael Khobalatte -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
