On Tue, Jan 20, 2009 at 3:45 AM, Greg Hauptmann <
[email protected]> wrote:
> Hi,
>
> I've just discovered the "named_scope" method which seems great. I'm
> wondering there is any reason why you wouldn't always use a named scope (to
> get the advantages), over a custom method on your model to return an array
> of records?
>
> That is using:
>
> class Shirt < ActiveRecord::Base
> named_scope :red, :conditions => {:color => 'red'}
> end
>
> instead of
>
> class Shirt < ActiveRecord::Base
> def red
>
> Shirt.find_all_by_color('red')
> end
> end
>
>
> Comments?
>
>
>
> --
> Greg
> http://blog.gregnet.org/
>
>
>
> >
>
The only reason to use a custom method instead of a named_scope is when
you're doing more than querying the db or there's something named_scopes
can't handle.
--
Andrew Timberlake
http://ramblingsonrails.com
http://www.linkedin.com/in/andrewtimberlake
"I have never let my schooling interfere with my education" - Mark Twain
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
