#27875: Manager inheritance for multi-table inheritance model behaviour
-------------------------------------+-------------------------------------
Reporter: ek-init | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution: invalid
Keywords: Manager inheritance | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
You are using Django < 1.10 while reading the documentation for Django >=
1.10.
As the [https://docs.djangoproject.com/en/1.10/topics/db/managers/#custom-
managers-and-model-inheritance Django 1.10 documentation mentions]:
> In older versions, manager inheritance varied depending on the type of
model inheritance (i.e. Abstract base classes, Multi-table inheritance, or
Proxy models), especially with regards to electing the default manager.
--
Ticket URL: <https://code.djangoproject.com/ticket/27875#comment:1>
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/065.33a58f46e5609df831fb73146916810a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
