#23076: Cascaded deletion of polymorphic models fails
-------------------------------------+-------------------------------------
Reporter: jernej@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jonathan Stray):
Aha! There is a simple workaround for 1.11, from this [https://github.com
/django-polymorphic/django-polymorphic/issues/229#issuecomment-246613138
django-polymorphic bug].
On the base class, set
{{{
class Animal(PolymorphicModel):
...
class Meta:
base_manager_name = 'base_objects
}}}
I have no idea why this works, or if this should ultimately be fixed in
`django` or `django-polymorphic`
--
Ticket URL: <https://code.djangoproject.com/ticket/23076#comment:18>
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.3b87e1d2e364a4bf311a35cc63c2c6f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
