Mysql2::Error: after updating to Rails 4.1

Question

I recently updated my Rails app from 4.0 to 4.1. Everything seems to work fine, except this one line in my Search Model that was working before.

Essentially, I want to search/find District_Resources by Tag Name and by the District_Resource Name.

**ex.**
If I search the word "Tutoring" 
*I should get all District_Resources with the Resource_Tag "Tutoring"
*And all District Resources that include the word Tutoring in it's Name. 
(i.e Tutoring Services)

For some reason, I keep getting this error:

(Mysql2::Error: Unknown column 'resource_tags.name' in 'where 
clause': SELECT `district_resources`.* FROM `district_resources`  
WHERE (resource_tags.name like '%Tutoring%' OR district_resources.name like '%Tutoring%')  
ORDER BY `district_resources`.`name` ASC):

But that column does exist in the Resource_Tags table.

MODELS

class DistrictResource < ActiveRecord::Base

  has_many :district_mappings, dependent: :destroy
  has_many :resource_tags, through: :district_mappings

  accepts_nested_attributes_for :resource_tags
end

class ResourceTag < ActiveRecord::Base

  has_many :district_mappings, dependent: :destroy
  has_many :district_resources, through: :district_mappings

end

class Search < ActiveRecord::Base

  def district_resources
    @district_resources ||= find_district_resources
  end

  def find_district_resources
    district_resources = DistrictResource.order(:name)

    district_resources = district_resources.includes(:resource_tags).where("resource_tags.name like :name OR district_resources.name like :name", {:name => "%#{name}%" })

    district_resources
  end

end

SCHEMA

create_table "district_resources", force: true do |t|
  t.string   "name"
  t.string   "description"
  t.string   "website"
  t.string   "phone"
  t.string   "email"
  t.datetime "created_at"
  t.datetime "updated_at"
end

create_table "district_mappings", force: true do |t|
  t.integer  "district_resource_id"
  t.integer  "resource_tag_id"
  t.datetime "created_at"
  t.datetime "updated_at"
end

create_table "resource_tags", force: true do |t|
  t.string   "name"
  t.datetime "created_at"
  t.datetime "updated_at"
end

`Mysql2::Error: Unknown column 'resource_tags.name'`. Did you double check that your test database has the expected structure? — spickermann, Aug 05 '15 at 18:41
I do not have a test database. This is a small personal project I was working on. So the test DB does not exist. Could that be the issue? If so, why didn't i have this problem before — Serge Pedroza, Aug 05 '15 at 18:46
I just created and migrated a test db. and I am still getting this error — Serge Pedroza, Aug 05 '15 at 19:00

score 1 · Accepted Answer · answered Aug 05 '15 at 20:42

You are referencing district_resources in where clause but this is not joined in query as you are eager loading resource_tags so here are two solutions for this

1.

district_resources = district_resources.joins(:resource_tags).where("resource_tags.name like :name OR district_resources.name like :name", {:name => "%#{name}%" })

2.

district_resources = district_resources.includes(:resource_tags).refereces(resource_tags).where("resource_tags.name like :name OR district_resources.name like :name", {:name => "%#{name}%" })

In both of these cases we are telling rails that we are using resource_tags table in where clause so join district_resources with it

score 0 · Answer 2 · answered Aug 05 '15 at 19:06

0

Fixed it!!

district_resources = district_resources.includes(:resource_tags).where("resource_tags.name like :name OR district_resources.name like :name", {:name => "%#{name}%" }).references(:resource_tags)

I had to reference the Resource_Tags Model

answered Aug 05 '15 at 19:06

Serge Pedroza

2,160
3
28
41

If this is your final answer, then please "accept" it – onebree Aug 05 '15 at 19:50
@HunterStevens i can't, i have to wait two days. – Serge Pedroza Aug 05 '15 at 20:28
If you feel the solution was basic typo error or stuff, I suggest closing it then – onebree Aug 05 '15 at 20:32
The fact that the accepted solution includes what you have, I suggest deleting this answer, as it is excessive now – onebree Aug 06 '15 at 12:36

Mysql2::Error: after updating to Rails 4.1

2 Answers2