Timeline for Double way parent child relationship in Django
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2020 at 19:30 | vote | accept | Rodrigo Caicedo | ||
| Jan 23, 2020 at 19:23 | answer | added | T. Sar | timeline score: 1 | |
| Jan 23, 2020 at 19:07 | comment | added | Rodrigo Caicedo | @T.Sar-ReinstateMonica Thanks for your comment, makes complete sense. Please put it as an aswer to my question to accept it. | |
| Jan 23, 2020 at 19:04 | comment | added | T. Sar | @RodrigoCaicedo Two rows certainly seems the way to do it. Having an extra "direction" field will force your app to add extra logic that wouldn't be needed otherwise. Database storage is cheap, codelines aren't. | |
| Jan 23, 2020 at 18:23 | comment | added | Rodrigo Caicedo | I don't have that table yet, but yes. One option is to create the table you mention, but that would mean to have two rows. I am not sure that is better than having only one row (or registry) and specify the "direction" of the permission in two different specific fields. | |
| Jan 23, 2020 at 18:21 | comment | added | Ant P | So you have a table containing two columns: permission holder and subject. Reciprocal permissions means two rows. | |
| Jan 23, 2020 at 18:20 | history | edited | BobDalgleish | CC BY-SA 4.0 |
Fixed spelling and grammar, Removed thanks.
|
| Jan 23, 2020 at 18:15 | review | First posts | |||
| Jan 23, 2020 at 18:20 | |||||
| Jan 23, 2020 at 18:15 | history | asked | Rodrigo Caicedo | CC BY-SA 4.0 |