Patrick, Thanks... I checked again and the example I posted was a bit off of my real example, which uses associations and scopes. According to the docs:
All \scopes are available as class methods on the ActiveRecord::Base descendent upon which the \scopes were defined. But they are also available to has_many associations. If, class Person < ActiveRecord::Base has_many :shirts end then elton.shirts.red.dry_clean_only will return all of Elton’s red, dry clean only shirts. So a better example would be: b = Blog.first b.entries.unseen I guess in this case, the method :unseen is bound to the set returned via the association, and not the class itself? Tom On Jan 15, 11:52 am, Patrick Doyle <wpds...@gmail.com> wrote: > On Thu, Jan 15, 2009 at 11:21 AM, Tom M <thomas.mack...@gmail.com> wrote: > > > I may be overlooking something, but it seems to me that it is a > > problem if with this code... > > > Class Blog < ActiveRecord::Base > > named_scope :unseen, :conditions => "displayed IS NULL" > > end > > > this test fails... > > > it "should give a list of unseen entries" do > > Blog.expects :unseen > > b = Blog.new > > b.unseen > > end > > > I don't know if this will help or not, but the little I've used named > > scopes, I've used them as class methods, not as instance methods, i.e. > Blog.unseen not b.unseen. > > --wpd --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---