#25520: Cascade delete of proxy model children fails with IntegrityErrors
-------------------------------------+-------------------------------------
Reporter: jmurty | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
This is really just a symptom of the issue described in #23076 and #25505
and should be closed as a duplicate.
IMO the correct fix would be to propagate reverse foreign keys from proxy
models to their concrete base (#18012) and then simply make sure the proxy
model deletion code always retrieve the reverse relationships from
concrete models.
--
Ticket URL: <https://code.djangoproject.com/ticket/25520#comment:6>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.8bc1378b632a1ff83cf46863b752f825%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
