Timeline for How to store 1:n self reference (dependencies) in relational database
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2016 at 21:06 | vote | accept | icehawk | ||
| Feb 20, 2016 at 20:56 | comment | added | Iker | @Ixrec I saw it well explained in another answer earlier (not sure if here or at StackOverflow): 1:N relationships are best thought of as optimizations of M:N relationships. And unless you're really, really sure that there's no way the 1:N will turn into more, you run smack into the old adage about premature optimization. | |
| Feb 20, 2016 at 20:46 | comment | added | Ixrec | Darn, I was writing a very similar answer but you went one step farther with it by dumping the dependency id entirely, which I should've thought of too. +1 | |
| Feb 20, 2016 at 20:44 | history | answered | Iker | CC BY-SA 3.0 |