Timeline for One generic mapping table VS many specific mapping tables
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2018 at 21:00 | history | tweeted | twitter.com/StackDBAs/status/1033821553170046976 | ||
| Aug 26, 2018 at 20:24 | history | edited | Solomon Rutzky | CC BY-SA 4.0 |
improved formatting
|
| Aug 26, 2018 at 20:19 | answer | added | Solomon Rutzky | timeline score: 2 | |
| Aug 25, 2018 at 12:00 | comment | added | Michael Green | See the discussion for this question | |
| Aug 25, 2018 at 6:43 | comment | added | sticky bit | As far as I understand the scenario the "generic" table has one big downside: It's impossible to define foreign key constraints from one column to different tables. One you have to build complex, error prone and comparatively slow triggers, to ensure integrity. And integrity is a very important point. | |
| Aug 25, 2018 at 1:15 | review | First posts | |||
| Aug 25, 2018 at 3:34 | |||||
| Aug 25, 2018 at 1:13 | history | asked | Jason | CC BY-SA 4.0 |