Timeline for Is having all entity tables inherit from one main entity table a bad idea?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Aug 13, 2012 at 12:31 | comment | added | Leigh Riffel | The point wasn't that it is violating a normal form, just that it is not necessary to satisfy normalization. | |
| Aug 10, 2012 at 17:12 | comment | added | Neil McGuigan | Which normal form is it violating though...? | |
| Aug 10, 2012 at 12:12 | comment | added | Leigh Riffel | @Joel Brown Excellent Point. | |
| Aug 10, 2012 at 1:52 | comment | added | Joel Brown | Good answer (+1). Having similar attributes (columns) on multiple entities (tables) doesn't necessarily mean they are redundant. You wouldn't think of dragging every name or description or cost field in a database together into a single table. That's not what normalization is about. Change tracking/soft deletion attributes are just the same. | |
| Aug 9, 2012 at 14:59 | history | answered | Leigh Riffel | CC BY-SA 3.0 |