Not sure how to do this

In an app I’m working on, I want to have a filter in which you can
specify certain attributes and click “filter” to activate an AJAX
request and return a list of, say, machines that match with those

No I’m not sure how to build the controller.

If I would specify all the attributes, I would simply do:

def filter
@machines = Machine.find(:all, :conditions => { :attr_1 => params
[:attr_1], :attr_2 … }

But how would I do this if only some of the attributes are specified
and the others are nil? Would I have to create @machines including all
machines and have Rails do the rest of the work or is there a way to
get find to do what I want?

Off the top of my head:
class Machine < ActiveRecord::Base
# Define a list of acceptable params for filtering
FILTERS = [:name, :code]

# Finds records by params
def self.filter_by_params(params)
  conditions = { |key,val| 

and val }
all(:conditions => conditions)

class MachinesController < ApplicationController
def index
# Where params is { :filter => { :name => ‘Pat’, :code => ‘123’ }}
@machines = Machine.filter_by_params(params[:filter])

Could you explain why the first part would go entirely into the
Machine model?

Could you explain why the first part would go entirely into the

Machine model?

Because it’s better to encapsulate
model logic in the models (and custom finders are model logic).
Controllers should only be responsible for receiving a request,
calling the appropriate model methods,
then returning a response.

  • Pat

You could try building up a chain of scopes - see this post:

As noted there, you can avoid cluttering up your model by using
‘scoped’ to create anonymous scopes.

So your example would look like:

in the controller action

proxy = Machine
[:attr1, :attr2, :attr3].each do { |k|
proxy = proxy.scoped(:conditions => Hash[k, params[k]]) unless params
@machines = proxy.find(:all)

That last find can also be a paginate, have limits, sorts, etc.

–Matt J.

Now that I read again, scoped won’t allow destroy_all to get through,
but I
still stand by my point :slight_smile:

That works, though it’s definitely a good idea to sanitize which params
be used in such a manner. Otherwise, someone could send params like {
:destroy_all => true } or something, and then there goes your database.

On 3 jul, 22:43, Pat N. [email protected] wrote:

  • Pat
    Thank you, that’s very clear!

I’ve decided to try and go with this solution as this actually does
what I inteded to do. I just had some trouble understanding why in
most examples this piece of code is put into the controller and you

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs