diff options
| author | Tim Graham <timograham@gmail.com> | 2017-02-24 16:15:36 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-02-24 16:15:36 -0500 |
| commit | 22eb15a18c16b93496f6e88ebe3a306daad492b1 (patch) | |
| tree | edb55c632ab2df3ec762dcced2290c6f585888f6 /docs | |
| parent | 5a85f2ca5fc3c4292cd1b147198d75d0f141fd71 (diff) | |
[1.11.x] Fixed #27875 -- Doc'd manager_inheritance_from_future in manager docs.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/managers.txt | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt index 2867db02d9..28eb32fbd6 100644 --- a/docs/topics/db/managers.txt +++ b/docs/topics/db/managers.txt @@ -369,8 +369,10 @@ Here's how Django handles custom managers and :ref:`model inheritance .. versionchanged:: 1.10 - In older versions, manager inheritance varied depending on the type of - model inheritance (i.e. :ref:`abstract-base-classes`, + Some inheritance behaviors described above don't apply unless you set + ``manager_inheritance_from_future = True`` on the model's ``Meta`` class. + In older versions and if you don't set that attribute, manager inheritance + varies depending on the type of model inheritance (:ref:`abstract-base-classes`, :ref:`multi-table-inheritance`, or :ref:`proxy-models`), especially with regards to electing the default manager. |