Hi, I added authentication to an app that already had a Person model. Rather than use the Person class to represent "Users" I created a User model and stored "users" in a users table. I now want to clean that up as my "People" can now also be "Users". My initial stab was to just migrate the authentication columns (encr. password, salt, login) to the Person model/table and simply get User to inherit from Person (I did not bother with using a STI type column): Person < ActiveRecord::Base ... end User < Person ... end Doing this I can still keep all of my authentication specific stuff in the User class - and all my other code just continues to work as expected, i.e. it is just an object storage change. This works as expected, but can anyone see any problems with this approach. My initial thought is the attributes that are locked down via the user class are now accessible via the Person class. Thanks is advance... James --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---