mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-31 01:25:32 +00:00
Code Issues 32 Releases Wiki Activity

[1.6.x] Fixed #23597 -- Clarified the manager that {Single,Multiple}ObjectMixin.model uses.

Browse Source 
Backport of e501d4c505 from master
This commit is contained in:
Ismail Badawi
2014-10-04 21:09:32 -04:00
committed by Tim Graham
parent e71ef9b6f2
commit 0aad1f1ea9
3 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/ref/class-based-views/mixins-multiple-object.txt
View File

@@ -56,7 +56,8 @@ MultipleObjectMixin
The model that this view will display data for. Specifying ``model The model that this view will display data for. Specifying ``model
= Foo`` is effectively the same as specifying ``queryset = = Foo`` is effectively the same as specifying ``queryset =
Foo.objects.all()``. Foo.objects.all()``, where ``objects`` stands for ``Foo``’s
:ref:`default manager <default-managers>`.
.. attribute:: queryset .. attribute:: queryset

3
docs/ref/class-based-views/mixins-single-object.txt
View File

@@ -16,7 +16,8 @@ SingleObjectMixin
The model that this view will display data for. Specifying ``model The model that this view will display data for. Specifying ``model
= Foo`` is effectively the same as specifying ``queryset = = Foo`` is effectively the same as specifying ``queryset =
Foo.objects.all()``. Foo.objects.all()``, where ``objects`` stands for ``Foo``’s
:ref:`default manager <default-managers>`.
.. attribute:: queryset .. attribute:: queryset

5
docs/topics/db/managers.txt
View File

@@ -169,6 +169,11 @@ For example::
This example allows you to request ``Person.men.all()``, ``Person.women.all()``, This example allows you to request ``Person.men.all()``, ``Person.women.all()``,
and ``Person.people.all()``, yielding predictable results. and ``Person.people.all()``, yielding predictable results.
.. _default-managers:
Default managers
~~~~~~~~~~~~~~~~
If you use custom ``Manager`` objects, take note that the first ``Manager`` 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 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 special status. Django interprets the first ``Manager`` defined in a class as