Timeline for Database design: Is there a much better way on this current relationships?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2015 at 17:59 | vote | accept | user3323654 | ||
| Apr 28, 2015 at 17:28 | answer | added | Neil McGuigan | timeline score: 1 | |
| Apr 28, 2015 at 13:09 | comment | added | user3323654 | Is there an another way around? | |
| Apr 28, 2015 at 12:56 | comment | added | SDillon | In practice what you're proposing is good. A good practice is to also have an AccountType table that will contain the friendly description of the account type and an integer. Then use that integer in the User table in the account type field. Any indexing on that field, in the user table, will be more efficient. You only need to join to the AccountType table when you care to display the friendly name. Also modifications to AccountType values will be much more efficient. | |
| S Apr 28, 2015 at 12:42 | history | suggested | Md Haidar Ali Khan | CC BY-SA 3.0 |
formatting
|
| Apr 28, 2015 at 12:40 | review | Suggested edits | |||
| S Apr 28, 2015 at 12:42 | |||||
| Apr 28, 2015 at 12:30 | history | asked | user3323654 | CC BY-SA 3.0 |