Timeline for Multiple many to many relations or one option table?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2014 at 10:56 | vote | accept | Beowulfenator | ||
| Jul 24, 2014 at 11:53 | comment | added | Beowulfenator | Thank you for your input. I've checked the article and I think they're not really being fair. Basically what they're saying is "it's much easier to get data from columns than have a N-N relation". For example, how would it be easier to get all persons with pet cat OR hobby TV if these are stored in separate tables vs. the proposed structure? Also, what benefits of relation DBMS am I missing? It seems that structural integrity is maintained and no redundant data is stored. | |
| Jul 24, 2014 at 5:09 | history | answered | Igby Largeman | CC BY-SA 3.0 |