Honestly, I've always preferred single-table inheritance. I am new to Rails, but in Java, this is what I've always done and it just works really nicely and it's more performant than forcing multiple joins whenever you want to query users - which is probably going to be often.
I am finding other problems that are Rails-specific with subclasses... like when submitting forms with simple_for, the parameters hash isn't the base class by default, so I am having trouble forcing it to be the base-class... but structurally, single-table inheritance is a sound practice. Been doing it for over a decade. -- 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.
