User table database best practices -


i wondering best practices organizing user data.

should store user data per row in 1 table or should cutting smaller chunks , using multiple tables related primary key?

for example.

to start want record personal info name, occupation, location etc. nice have option add usage history. in how many , surveys filled out , articles commented on.

while typing makes sense me have table comments table username+password, table personal info , keep adding tables needs grow...

would confirmation though.

if there going one-to-many relations should split up, things one-to-one shouldn't. if user going have multiple addresses, phone numbers, history, friends, etc, have addresses table (or phone numbers, history, or friends tables) tied customer's id.

for username , password wouldn't need separate table.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -