From e501d4c505ede0c87c2d1a8667167314021489e2 Mon Sep 17 00:00:00 2001 From: Ismail Badawi Date: Sat, 4 Oct 2014 21:09:32 -0400 Subject: [PATCH] Fixed #23597 -- Clarified the manager that {Single,Multiple}ObjectMixin.model uses. --- docs/ref/class-based-views/mixins-multiple-object.txt | 3 ++- docs/ref/class-based-views/mixins-single-object.txt | 3 ++- docs/topics/db/managers.txt | 5 +++++ 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/ref/class-based-views/mixins-multiple-object.txt b/docs/ref/class-based-views/mixins-multiple-object.txt index 193203be6d..8d64604841 100644 --- a/docs/ref/class-based-views/mixins-multiple-object.txt +++ b/docs/ref/class-based-views/mixins-multiple-object.txt @@ -56,7 +56,8 @@ MultipleObjectMixin The model that this view will display data for. Specifying ``model = Foo`` is effectively the same as specifying ``queryset = - Foo.objects.all()``. + Foo.objects.all()``, where ``objects`` stands for ``Foo``’s + :ref:`default manager `. .. attribute:: queryset diff --git a/docs/ref/class-based-views/mixins-single-object.txt b/docs/ref/class-based-views/mixins-single-object.txt index 2f48841463..8296064c15 100644 --- a/docs/ref/class-based-views/mixins-single-object.txt +++ b/docs/ref/class-based-views/mixins-single-object.txt @@ -16,7 +16,8 @@ SingleObjectMixin The model that this view will display data for. Specifying ``model = Foo`` is effectively the same as specifying ``queryset = - Foo.objects.all()``. + Foo.objects.all()``, where ``objects`` stands for ``Foo``’s + :ref:`default manager `. .. attribute:: queryset diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt index 73f3bacd00..3c0c3f3fb8 100644 --- a/docs/topics/db/managers.txt +++ b/docs/topics/db/managers.txt @@ -169,6 +169,11 @@ For example:: This example allows you to request ``Person.authors.all()``, ``Person.editors.all()``, and ``Person.people.all()``, yielding predictable results. +.. _default-managers: + +Default managers +~~~~~~~~~~~~~~~~ + If you use custom ``Manager`` objects, take note that the first ``Manager`` Django encounters (in the order in which they're defined in the model) has a special status. Django interprets the first ``Manager`` defined in a class as