#33586: Applying RunPython backward results in ValueError when involved models
are
referenced through multiple foreign keys
-------------------------------+------------------------------------
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
-------------------------------+------------------------------------
Changes (by Simon Charette):
* summary:
Cannot delete object (A) referenced by another object (B) if said
object (A) has a foreign key to a custom user.
=>
Applying RunPython backward results in ValueError when involved models
are referenced through multiple foreign keys
Comment:
#36161 was a duplicate that demonstrated the problem can be triggered even
without a custom user model.
I'm going to rename this ticket to better capture the generic nature of
the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/33586#comment:29>
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/01070194d998aff6-a91cb527-5301-4929-8b32-ac65d91dd4c8-000000%40eu-central-1.amazonses.com.
