Comments on: Filtering with named scopes

By: Phil Kursawe

Phil Kursawe — Wed, 17 Mar 2010 15:37:36 +0000

Just found this blog entry. Nice one. Would it also be possible to combine several selected filters like “:adult, :adults”?

By: Iain Hecker

Iain Hecker — Sun, 14 Jun 2009 09:30:42 +0000

@Edwin I understand your concern.

I like the way it works in DataMapper, in which you can chain any method. The query only gets executed once you try to read a record from the set.

There is a proper use and balance for everything. So with this. I like the flexibility of it, because you can use the “filter_*”-methods in any place.

And I don’t think controllers is the place to use “send”. I like to keep the more rubyesque methods out of there. But then again, there is no absolute rule for anything.

By: Edwin Vlieg

Edwin Vlieg — Fri, 12 Jun 2009 18:29:20 +0000

Nice article, but I'm wondering if this is the right way to go. The purpose of named_scope is to defined named scopes. Just defining a filter scope which accepts a name for the scope isn't really the way to go in my opinion. You can find my approach on the BlueTools weblog (dutch). As you can see, I'm using a new named_scope for each filter. Only for the advanced filtering in which the user can define the conditions for the filter, I'm using the approach you are taking.