Avoid one-to-one relation table?
Posted by:
Dave Java
Date: March 17, 2006 02:24PM
A User table has one to one relation to UserProfile table.
A User has one UserProfile.
Tables:
User (username, password)
UserProfile (firstname, lastname, address, phone, security question, ...)
When a user login, A User row needs to be read from database. But UserProfile is read from database only when user want to see/edit his/her profile.
For one-to-one relation design, should I merge User and UserProfile table to become one table? what are pros and cons? Thanks!
Subject
Written By
Posted
Avoid one-to-one relation table?
March 17, 2006 02:24PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.