Timeline for Should I break a large user table into smaller tables for specific roles and information?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10 at 11:11 | comment | added | Albert Godfrind | As for performance, you talk about thousands of users which should not be any issue. | |
| Dec 10 at 11:07 | comment | added | Albert Godfrind | Separating work and education into separate tables seems fundamental to me, since each user can have multiple occupations (historically or even simultaneously). Same for education. This is normalization 101. It is definitely best for maintainability. | |
| Dec 10 at 1:33 | answer | added | Rick James | timeline score: 1 | |
| Dec 10 at 1:09 | review | Suggested edits | |||
| Dec 10 at 14:22 | |||||
| Dec 10 at 1:09 | comment | added | philipxy | Ask 1 specific researched non-duplicate question per post. PS Including, not asking multiple questions via AND & OR. Yes or no questions are seldom useful or asking what the asker actually wants answered. Given this post clearly your questions are very likely to be duplicates already asked & answered many times. PS Please avoid social & meta commentary in posts. | |
| Dec 10 at 1:04 | comment | added | philipxy | Splitting into smaller tables for subtypes is not DB normalization. Why do you think it is? If you ask about it explain why you think it is & how you are 1st stuck. | |
| Dec 9 at 23:04 | comment | added | Bill Karwin | You haven't shown any queries you will use to query these data. Performance strategies must be chosen in the context of the specific queries you need to optimize. Every optimization strategy optimizes one type of query at the expense of other types of queries, so you need to know which queries are the priority. | |
| S Dec 9 at 21:09 | review | First questions | |||
| Dec 10 at 8:06 | |||||
| S Dec 9 at 21:09 | history | asked | JayDev95 | CC BY-SA 4.0 |