#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: Bhuvnesh
Type: Bug | Status: assigned
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Jeremy Poulin):
My interpretation of Simon's work is that the patch in question would
address the deficiency in the .apps cache invalidation logic.
>The apps that are attached to the modesl is simply wrong when the
migration is applied backward. It seems the .apps cache invalidation logic
in MigrationExecutor._migrate_all_backwards and its subsequent call
doesn't account for a particular case that still needs to be determined.
While the workaround provided does allow us to move forward, I don't think
submitting it as a fix is the best way forward. I would liken it to
putting a poster up to cover a whole in the wall. It gets the job done,
but masks the root cause.
--
Ticket URL: <https://code.djangoproject.com/ticket/33586#comment:9>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018337382be4-72eaab19-3964-4d8b-ae2a-7cf7b999c4b5-000000%40eu-central-1.amazonses.com.
