【问题标题】:In Rails, how to connect a model twice to another model that it polymorphically belongs_to?在 Rails 中,如何将一个模型两次连接到它多态属于的另一个模型?
【发布时间】:2014-09-04 20:07:07
【问题描述】:

我正在尝试确定在 Rails 4 中设置以下架构和关联的适当方法:

Business
  company_name
  ->1 street_address (Address)
  ->0..1 mailing_address (Address)
  ->0..n employees (Employee)

Employee
  first_name
  last_name
  birthday
  ->0..n addresses (Address)

Address
  street
  city
  state
  zip
  ->1 resource (Business or Employee or potentially something else in the future)

这里的主要目标是:

  1. 能够检索任意地址,进而找到它所属的资源(可能是企业或员工)
  2. 将一个地址指定为每个企业的“街道地址”,并可选择将另一个地址指定为“邮寄地址”
  3. 允许每个企业拥有多个员工,每个员工可能有其他不同的地址(家庭住址等)。
  4. 允许其他未来的资源(目前未知)也有关联的地址

请注意,地址可以属于企业(充当街道地址或企业的邮寄地址),也可以属于员工(员工可以有多个地址)。这对我来说意味着多态关系,我在 Rails 中实现它的第一次尝试是这样的:

class Business < ActiveRecord::Base
  has_one :street_address, class_name: 'Address', as: :resource, 
                           inverse_of: :resource, dependent: :destroy
  has_one :mailing_address, class_name: 'Address', as: :resource, 
                            inverse_of: :resource, dependent: :destroy
  has_many :business_employees, inverse_of: :business, dependent: :destroy
  has_many :employees, through: :business_employees
end

class BusinessEmpoloyee < ActiveRecord::Base
  belongs_to :business
  belongs_to :employee
end

class Employee < ActiveRecord::Base
  has_many :business_employees, inverse_of: :employee, dependent: :destroy
  has_many :businesses, through: :business_employees
  has_many :addresses, as: :resource, inverse_of: :resource, dependent: :destroy
end

class Address < ActiveRecord::Base
  belongs_to :resource, polymorphic: true
end

但是,这并没有像希望的那样工作。商家的街道地址和邮寄地址始终返回相同的值。例如:

2.1.2 :001 > b = Business.create(company_name: 'Test Business')

2.1.2 :002 > b.street_address = Address.create(street: '123 Main St', city: 'San Francisco', state: 'CA')

2.1.2 :003 > b.mailing_address = Address.create(street: 'P.O. Box 123', city: 'New York', state_code: 'NY')

2.1.2 :004 > b2 = Business.find_by_company_name('Test Business')
  Business Load (1.2ms)  SELECT  "businesses".* FROM "businesses"  WHERE "businesses"."company_name" = 'Test Business' LIMIT 1
 => #<Business id: 1168, company_name: "Test Business", street_address_id: nil, mailing_address_id: nil, created_at: "2014-09-04 19:57:14", updated_at: "2014-09-04 19:57:14"> 

2.1.2 :005 > b2.mailing_address
  Address Load (0.5ms)  SELECT  "addresses".* FROM "addresses"  WHERE "addresses"."resource_id" = $1 AND "addresses"."resource_type" = $2 LIMIT 1  [["resource_id", 1168], ["resource_type", "Business"]]
 => #<Address id: 1186, resource_id: 1168, resource_type: "Business", street: "P.O. Box 123", city: "New York", state: "NY", zip: nil, created_at: "2014-09-04 19:57:56", updated_at: "2014-09-04 19:57:56"> 

2.1.2 :006 > b2.street_address
  Address Load (0.5ms)  SELECT  "addresses".* FROM "addresses"  WHERE "addresses"."resource_id" = $1 AND "addresses"."resource_type" = $2 LIMIT 1  [["resource_id", 1168], ["resource_type", "Business"]]
 => #<Address id: 1186, resource_id: 1168, resource_type: "Business", street: "P.O. Box 123", city: "New York", state: "NY", zip: nil, created_at: "2014-09-04 19:57:56", updated_at: "2014-09-04 19:57:56"> 

当然,这确实是有道理的——企业应该如何知道哪个地址用于哪个地址值?

那么,既然如此,关于我如何捕捉这里描述的关系有什么建议吗?

【问题讨论】:

    标签: ruby-on-rails ruby ruby-on-rails-4 rails-activerecord polymorphic-associations


    【解决方案1】:

    经验法则:关系被写入belongs 的模型中。如果您为一个模型指定两个指向同一个模型的关联,它们实际上是相同的,因为只有一种归属方式:拥有某个模型的 resource_idresource_type

    您需要在“归属”中添加另一个参数,以过滤“那是什么类型的归属”。一种相当标准的方法是单表继承 (STI)(和I happened to write about how to use it),其工作原理如下:将type:string:index 列添加到Address 并创建一个继承自Address 的新类,例如, MailingAddress:

    class MailingAddress < Address
    end
    

    大多数情况下它应该是空的,它继承了Address的所有内容,甚至存储:它存储在同一个表中,但可以通过type="MailingAddress"进行区分,type="MailingAddress"会在您查询此类的实例时自动添加从数据库。但是,根据继承原则,当您查询 Addresses 时,您也会得到 MailingAddresses。

    做同样的事情的其他方法涉及类似的事情:添加另一列以从所有其他列中过滤掉邮寄地址。字符串并不是比较快的东西,尽管 RDBMS 在这方面的速度非常快。

    【讨论】:

      猜你喜欢
      • 2017-04-24
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2016-07-02
      • 2020-08-10
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多