#29386: Meta Inheritance for default_permissions
-------------------------------------+-------------------------------------
Reporter: Clayton Daley | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
That section if for abstract inheritance, one of the three types (the
others being multi-table and proxy). It's saying that when you inherit
from an abstract model Meta is inherited (and can be overridden.)
Your case is Proxy inheritance, which links to the multi-table rules for
inheritance (which I cited above). It's important not to conflate the
different types of inheritance.
I appreciate it's complex and not always as expected every time,
especially when the examples become more developed, as are yours.
This still seems to be expected behaviour. I'm going to close this as
such. If you have a concrete suggestion for the docs—there's always the
possibility of improvement—we'd be very happy to review a PR referencing
this issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/29386#comment:7>
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/070.4123c6294106785c75a883ac746d1535%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
