I''m creating an application that will have a user creating an account. Should I split the user model into two? user, user_info. user will contain the essential: id, login, hashed_password user_info will contain all the other information: first name, last name, address, etc. I plan to have the user login and store its user model into the session. This way, it does not need to store the user_info model into the session. Also, when logging in, the login search for the user will be quicker due to a smaller table size. Is this a good idea? Any possible problems down the road? Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---