Kevin Hastie wrote: [...] > j) What seems much easier is to have the Business and School tables to > each have an address_id, and be done with it.
That's correct. > That's what I would have > done days ago were I programming a language without so many "handy" > shortcuts. But to do so, doesn't it have to be > > Address > has_one :business > has_one :school > > Business > belongs_to :address > > That doesn't seem right..? That's only right if you want an address to treat associated businesses and schools differently. If you just want an address to have_one (or more likely many) associated generic entities, then you need polymorphism. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
