Forum: Ruby on Rails User accounts

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
A878ddd72afd550916074d25f5e94cc2?d=identicon&s=25 wheels (Guest)
on 2007-04-02 09:04
(Received via mailing list)
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?

This topic is locked and can not be replied to.