From 22eb15a18c16b93496f6e88ebe3a306daad492b1 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 24 Feb 2017 16:15:36 -0500 Subject: [PATCH] [1.11.x] Fixed #27875 -- Doc'd manager_inheritance_from_future in manager docs. --- docs/topics/db/managers.txt | 6 ++++-- 1 file 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.