#23076: Cascaded deletion of polymorphic models fails
-------------------------------------+-------------------------------------
Reporter: jernej@… | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by carljm):
* status: new => closed
* resolution: => wontfix
Comment:
I don't think this is a bug in Django, or Django's problem to fix. The
patch adds ~40 new lines of code to the deletion collector and makes it
significantly more complicated (and almost certainly introduces
performance regressions; one of them is even called out with a `FIXME` in
the patch), all to support something which violates one of the basic
assumptions of the Django ORM (that querysets are homogenous).
Closing as wontfix.
--
Ticket URL: <https://code.djangoproject.com/ticket/23076#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.634e181d7a9cb2ffb0cc55cd0a5d48fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
