Chaining queries in ActiveRecord

Hi all,

Stuck at this problem for several days. Tried to use named_scope,
scope_out, and plugin such as searchlogic, but no result.

The problem is as follows: I have a pic table and tag table, and a
join table called pic_tag (with only pic_id and tag_id) so that I can
associate N pics to M tags. This is the tutorial way to set up a many-
to-many association. I’m trying to implement a simple search function,
so that I can search for a picture with several given tags.

Now say I want to search for pics that are tagged with “dog” and
“cat”. The simplest way to do this is to use named_scopes, for

class Pic < ActiveRecord::Base
  has_many :pic_tags
  has_many :tags, :through => :pic_tags

  named_scope :dog, options_for_tag(“dog") # options_for_tag(tag) is a
method to generate joined table search conditions, not important
  named_scope :cat, options_for_tag("cat")

But when I chain the query like this:

The SQL query that I’m actually getting is the merged conditions:

SELECT "pics".* FROM "pics" INNER JOIN "pic_tags" ON ("pics"."id" =
"pic_tags"."pic_id") INNER JOIN "tags" ON ("tags"."id" =
"pic_tags"."tag_id") WHERE (( LIKE 'dog') AND ( LIKE

And the above query won’t give me any result, since no joined table
entry will have both ‘dog’ and ‘cat’ at the same time. The reason for
this is that using named_scope, query is done only when all the query
conditions are merged together. I tried scope_out, searchlogic plugin,
but they all share the same basic concept of using named_scope, so the
result is the same.

So here’s my question: is there any way to query step by step? If so,
then should be able to return all pics tagged with “dog”, and
then when I continue to query on the result, say,, I can
have all pics tagged with “cat” based on the previous result.

On Jan 15, 4:25Â pm, parkurm [email protected] wrote:

method to generate joined table search conditions, not important
“pic_tags”.“tag_id”) WHERE (( LIKE ‘dog’) AND ( LIKE

The classical way to handle this is to alias the tables involved so
they don’t get fused together by the SQL generation code.

For instance:

named_scope :dog, :joins => ‘INNER JOIN pic_tags AS dog_pic_tags ON
( =
dog_pic_tags.pic_id) INNER JOIN tags AS dog_tags ON ( =
dog_pic_tags.tag_id)’, :conditions => [‘ LIKE ?’, ‘dog’]

This gives each scope its own set of distinct joins, so it should
avoid the previous problem. It’s straightforward to extend this to a
named_scope named tagged_with:

named_scope :tagged_with, lambda { |n| { :joins => “INNER JOIN
pic_tags AS #{n}_pic_tags ON ( = #{n}_pic_tags.pic_id) INNER
JOIN tags AS #{n}_tags ON (#{n} = #{n}
_pic_tags.tag_id)”, :conditions => ["#{n} LIKE ?’,n] } }

Then you can do things like:

Pic.tagged_with(‘dog’).tagged_with(‘cat’) etc.

Note that you’ll want to sanitize any user inputs you’re passing to

–Matt J.

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