#36161: Deletion in reverse data migration fails with a chain of at least 3
foreign
keys
-----------------------------+-------------------------------------
Reporter: Enrico Zini | Owner: (none)
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+-------------------------------------
Changes (by Simon Charette):
* resolution: => duplicate
* status: new => closed
Comment:
I'm pretty confident this is a duplicate of #33586 (reverse migration,
cascade deletion, corrupted model cache) which will unfortunately be very
hard to solve the current model invalidation optimization strategy didn't
account for backward migration.
I guess a strategy could be to systematically clear the model cache when
applying migration in reverse order but that will cost at a significant
cost in performance unless #29898 is implemented.
I'm going to close this ticket as a duplicate to consolidate efforts and
discussions on this front given #33586 predates this ticket and has a bit
more discussions on the topic.
--
Ticket URL: <https://code.djangoproject.com/ticket/36161#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194d98fb677-610307e9-a715-4e4e-b29d-f05032977089-000000%40eu-central-1.amazonses.com.
