KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I have one primary key (say the user's ID), and I have tons of information associated with that user. The way I used to do it was to have multiple tables, so say, one table for application usage data, one table for profile info, one table for back end tokens etc. to keep things looking organized. Recently some one told me that it's better not to do it that way and having a table with lots of columns is fine. The thing is, all those columns have the same primary key. What are the pros and cons of multiple tables broken down into categories vs one table with many columns? What's the conventional way of doing it?
Tags (comma-separated)
Save Edits
Cancel