InventoryTrackers wrote: > Jake, > I couldn't help but feel sorry for you in the path you're taking. > Simply create a has_one and belongs_to relationship between a > controlling master record such as Student_Type(Teacher, Student, etc).
This is what the OP was originally planning. It is a bad idea for the reasons I outlined above. > Now, when you call a record its @student_type.users(find ??). > That inheritence stuff is for the race car drivers and opens up many > potholes that could CRASH your effort. You are absolutely wrong. It's the proper way to do it. It's not for "race car drivers", merely for developers who actually care about modeling their data correctly Inheritance is not difficult to work with, and every OO developer should understand it. Incorrect data modeling such as you are advocating, however, *will* crash your effort. > Hope this makes your life a little easier. It will not. > David 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 -~----------~----~----~----~------~----~------~--~---
