>> It is just so natural to use the same primary key in this situation. > > Why?
Well, it seems natural to me, and i often trust my senses :). I have been playing with it in console for a few minutes now and observing some fun and weird behavior: i = Instructor.create i.id # => 1 i.person_id # => nil Instructor.find(1) # => NoMethodError: undefined method `eq' for nil:NilClass ... i=Instructor.find_by_person_id(1) i.id # => nil i.person_id # => 1 So far it seem to be possible to find ways around to make it work, but i wonder if i am not making a philosophical mistake indeed, and if it will not break in new versions of rails ... -- 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.
