Browse files

Fixed #6541: Corrected documentation of how the admin chooses a defa…

…ult manager. Refs #6538.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
ubernostrum committed Mar 18, 2008
1 parent ebf3cde commit 41d101e9ce10ab08051db47500f24a701b6882e9
Showing with 9 additions and 8 deletions.
  1. +9 −8 docs/model-api.txt
@@ -1788,14 +1788,15 @@ For example::
This example allows you to request ````, ``Person.women.all()``,
and ``Person.people.all()``, yielding predictable results.
-If you use custom ``Manager`` objects, take note that the first ``Manager``
-Django encounters (in order by which they're defined in the model) has a
-special status. Django interprets the first ``Manager`` defined in a class as
-the "default" ``Manager``. Certain operations -- such as Django's admin site --
-use the default ``Manager`` to obtain lists of objects, so it's generally a
-good idea for the first ``Manager`` to be relatively unfiltered. In the last
-example, the ``people`` ``Manager`` is defined first -- so it's the default
+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 this first
+``Manager`` defined in a class as the "default" ``Manager``, and
+several parts of Django (though not the admin application) will use
+that ``Manager`` exclusively for that model. As a result, it's often a
+good idea to be careful in your choice of default manager, in order to
+avoid a situation where overriding of ``get_query_set()`` results in
+an inability to retrieve objects you'd like to work with.
Model methods

0 comments on commit 41d101e

Please sign in to comment.