#33586: Cannot delete object (A) referenced by another object (B) if said object
(A) has a foreign key to a custom user.
-------------------------------+------------------------------------
Reporter: Jeremy Poulin | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Timothy Schilling):
Is it possible that `migration_plan` is returning the wrong plan for
backwards migrations? As per my investigation
[https://code.djangoproject.com/ticket/35652#comment:description here] it
appears that when the migration to be unapplied is encountered, that some
of the other migrations hadn't applied their state.
I think it makes sense to start with all apps having their forward state
applied before storing the project state for a migration to be unapplied.
--
Ticket URL: <https://code.djangoproject.com/ticket/33586#comment:28>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701910fe64cae-46e2eac7-312b-46dc-ab93-a594ab884d8b-000000%40eu-central-1.amazonses.com.
