Timeline for IS-A relationship with only single sub entity
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2015 at 11:56 | vote | accept | farid_92 | ||
| Dec 12, 2015 at 3:12 | history | tweeted | twitter.com/StackDBAs/status/675513426546925568 | ||
| Dec 10, 2015 at 12:38 | answer | added | infiniteLoop | timeline score: 3 | |
| Dec 8, 2015 at 20:20 | history | edited | Hannah Vernon♦ |
edited tags
|
|
| Dec 8, 2015 at 19:31 | comment | added | farid_92 | @Dave Thanks for the answer, by the way I'm always doubtful about designing database, is there any book you can recommend me for mastering system analysis? | |
| Dec 8, 2015 at 19:12 | comment | added | Dave | You've created a subtype which is a good normalization technique. Sounds like it meets your requirements here... so you should be fine. For a full fledged (e.g. OED) database you might find too many unique elements to create such a design though. | |
| Dec 8, 2015 at 19:05 | history | edited | farid_92 |
edited tags
|
|
| Dec 8, 2015 at 18:48 | review | First posts | |||
| Dec 8, 2015 at 19:03 | |||||
| Dec 8, 2015 at 18:45 | history | asked | farid_92 | CC BY-SA 3.0 |