I'm creating an application that will have a user creating an
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?