Lighthouse ticket:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4452
I have recently been working on some gems that utilize
ActiveSupport::Cache and ran into some issues with the different
implementations handling the same functionality differently. One of
the issues was th
Alright, I see. Thanks for the info!
*waiting for 3.1* ;)
On Apr 21, 1:56 pm, Pratik wrote:
> I thought about doing that. But the current behaviour is for
> consistency with with_scope :
>
> >> User.send(:with_scope, :find => {:select => 'id'}) { User.first(:select =>
> >> "name") }
>
> User
I thought about doing that. But the current behaviour is for
consistency with with_scope :
>> User.send(:with_scope, :find => {:select => 'id'}) { User.first(:select =>
>> "name") }
User Load (0.3ms) SELECT name FROM `users` LIMIT 1
Maybe we can change the behaviour for 3.1 though.
On Wed,
Hey there,
I was just playing around with Beta3 and noticed that
Page.select(:id).select(:title).all was ignoring the first select.
Personally I'd prefer it to be merged together which seems easy from
my naive point of view but I'd also be happy if the docs would state
that it is not chainable or
