Changes between Initial Version and Version 1 of Ticket #24576
- Timestamp:
- Apr 3, 2015, 1:00:23 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #24576
- Property Triage Stage Unreviewed → Accepted
-
Ticket #24576 – Description
initial v1 1 I've spent all day with a bug on my application that seems to be a bug on Django's ORM delete on cascade reso ultion order.1 I've spent all day with a bug on my application that seems to be a bug on Django's ORM delete on cascade resolution order. 2 2 3 3 Moreover because the order in which related objects are deleted by the ORM is non-deterministic (changes every time you start the interpreter) it makes even harder to track down. … … 59 59 }}} 60 60 61 In order to properly test this you should make tries restarting the interpreter a handful l of times, and then you'll se two different results.61 In order to properly test this you should make tries restarting the interpreter a handful of times, and then you'll see two different results. 62 62 63 63 This that I consider correct: … … 100 100 101 101 102 Notice how the order in which related objects are deleted is differ net, I believe this to be the source of the problem.102 Notice how the order in which related objects are deleted is different, I believe this to be the source of the problem. 103 103 104 104 I've noticed this problem on 1.7 and now 1.8, not tested with master.