From f7814cdfe6c3b6d87bb8afdcc5c27ee2e92a6a62 Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Tue, 6 Apr 2010 11:52:32 +0000 Subject: [PATCH] Fixed #13035 - Incorrect documentation regarding admin and default managers Thanks to rasca for report and gabrielhurley for patch git-svn-id: http://code.djangoproject.com/svn/django/trunk@12930 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/db/managers.txt | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt index 4569775652..123408b2bb 100644 --- a/docs/topics/db/managers.txt +++ b/docs/topics/db/managers.txt @@ -167,15 +167,14 @@ For example:: This example allows you to request ``Person.men.all()``, ``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 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. +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 +the "default" ``Manager``, and several parts of Django will use that ``Manager`` +exclusively for that model. As a result, it's a good idea to be careful in +your choice of default manager in order to avoid a situation where overriding +``get_query_set()`` results in an inability to retrieve objects you'd like to +work with. .. _managers-for-related-objects: