2011-10-04 9 views
5

Cuando uso has_one funciona perfectamente, pero no en has_many. Aquí puede ver que object_id es diferente porque ejecutó otro SQL para recuperarlo nuevamente.¿Inverse_of funciona con has_many?

ruby-1.9.2-p290 :001 > e = Employee.create(name: 'rafael', active: false) 
ruby-1.9.2-p290 :002 > b = Badge.create(number: 1, employee: e) 
ruby-1.9.2-p290 :003 > a = Address.create(street: "123 Market St", city: "San Diego", employee: e) 
ruby-1.9.2-p290 :004 > e = Employee.first 
    Employee Load (0.2ms) SELECT "employees".* FROM "employees" LIMIT 1 
=> #<Employee id: 1, name: "rafael", active: false, created_at: "2011-10-04 17:09:25", updated_at: "2011-10-04 17:09:25"> 
ruby-1.9.2-p290 :002 > e.is_active? 
=> false 
ruby-1.9.2-p290 :003 > e.object_id 
=> 2182895380 
ruby-1.9.2-p290 :004 > e.badge.employee.is_active? 
    Badge Load (17.6ms) SELECT "badges".* FROM "badges" WHERE "badges"."employee_id" = 1 LIMIT 1 
=> false 
ruby-1.9.2-p290 :005 > e.badge.employee.object_id 
=> 2182895380 
ruby-1.9.2-p290 :006 > e.addresses.first.employee.is_active? 
    Address Load (0.2ms) SELECT "addresses".* FROM "addresses" WHERE "addresses"."employee_id" = 1 LIMIT 1 
    Employee Load (0.3ms) SELECT "employees".* FROM "employees" WHERE "employees"."id" = 1 LIMIT 1 
=> false 
ruby-1.9.2-p290 :007 > e.addresses.first.employee.object_id 
    Address Load (0.3ms) SELECT "addresses".* FROM "addresses" WHERE "addresses"."employee_id" = 1 LIMIT 1 
    Employee Load (0.2ms) SELECT "employees".* FROM "employees" WHERE "employees"."id" = 1 LIMIT 1 
=> 2181302220 
ruby-1.9.2-p290 :008 > 

Este es el código que he utilizado para configurar mi prueba:

class Employee < ActiveRecord::Base 
    has_many :addresses, :inverse_of => :employee 
    has_one :badge, :inverse_of => :employee 

    accepts_nested_attributes_for :addresses 
    accepts_nested_attributes_for :badge 
    # validates_associated :addresses 

    def is_active? 
    active 
    end 
end 

class Address < ActiveRecord::Base 
    belongs_to :employee, :inverse_of => :addresses 

    validates :city, length: { within: 100..1000, message: "Too short"}, :if => lambda {|a| a.employee.is_active?} 
end 

class Badge < ActiveRecord::Base 
    belongs_to :employee, :inverse_of => :badge 

    validates :number, length: { within: 2..10, message: "Too long"}, :if => lambda {|b| b.employee.is_active?} 
end 
+0

posible duplicado de [ActiveRecord: inversa \ _of no funciona en cuenta \ _many: a través del modelo de unirse en crear] (http: //stackoverflow.com/questions/7436173/activerecord-inverse-of-does-not-work-on-has- many -through-on-the-join-model-on) –

Respuesta

4

sí lo hace! Consulte la sección Asociaciones bidireccionales de los documentos API para Asociaciones en registro activo aquí: http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html

+3

"for belongs_to associations has_many asociaciones inversas se ignoran " ??? – bdwain

+0

Sí, creo que [estos documentos] (http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html#label-Bi-directional+associations) son muy confusos. El ejemplo da 'has_many: traps, inverse_of:: dungeon', pero en el párrafo siguiente dice: * for belongs_to associations has_many asociaciones inversas son ignoradas *. – dukedave

+0

La respuesta de Naoyoshi es correcta. Esta respuesta está desactualizada o incorrecta. – believesInSanta

5

No, no lo es. De acuerdo con Rails Guide,

  • No funcionan con: a través de asociaciones.
  • No funcionan con: asociaciones polimórficas.
  • No funcionan con: como asociaciones.
  • Para las asociaciones belongs_to, se han ignorado las asociaciones inversas de has_ ​​many.
Cuestiones relacionadas