Timeline for Correct organization of the database structure and selection
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2018 at 9:03 | vote | accept | ilw | ||
| S Jan 22, 2018 at 9:03 | history | bounty ended | ilw | ||
| S Jan 22, 2018 at 9:03 | history | notice removed | ilw | ||
| Jan 21, 2018 at 17:46 | history | edited | Evan Carroll |
edited tags
|
|
| Jan 18, 2018 at 8:58 | history | edited | ilw | CC BY-SA 3.0 |
added 27 characters in body
|
| Jan 17, 2018 at 16:42 | answer | added | Evan Carroll | timeline score: 2 | |
| Jan 17, 2018 at 16:11 | answer | added | derBjörn | timeline score: 3 | |
| S Jan 16, 2018 at 12:57 | history | bounty started | ilw | ||
| S Jan 16, 2018 at 12:57 | history | notice added | ilw | Draw attention | |
| Jan 16, 2018 at 9:00 | history | edited | ilw | CC BY-SA 3.0 |
added 30 characters in body
|
| Jan 16, 2018 at 6:48 | comment | added | Basil Bourque |
You’ve not explained enough, but it seems that if you meant each entity can have any number of “property”values assigned, those should be moved into a separate child table. For example, a person table should have a child table phone for zero, one, or more phone numbers (work, home, day, night, mobile, landline, in-case-of-emergency, etc.).
|
|
| Jan 14, 2018 at 12:42 | review | First posts | |||
| Jan 14, 2018 at 13:42 | |||||
| Jan 14, 2018 at 12:38 | history | asked | ilw | CC BY-SA 3.0 |