summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorBrendan Hayward <brendanhayward85@gmail.com>2015-05-08 22:52:15 +0500
committerTim Graham <timograham@gmail.com>2015-08-11 10:14:44 -0400
commitc9fb4f3c45b668c9a32f9ecdfe404566657df88e (patch)
tree7e57549574d4407fcf77d672aed7afa9af889276 /docs/topics
parent7fa1dd8a80795d7573fe650014c5d23af7557bc7 (diff)
Fixed #25205 -- Removed doc references to deprecated GeoManager class.
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/db/managers.txt14
1 files changed, 5 insertions, 9 deletions
diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt
index bd46a34c07..ae5bed536f 100644
--- a/docs/topics/db/managers.txt
+++ b/docs/topics/db/managers.txt
@@ -455,13 +455,10 @@ Throughout this section, we will use the term "automatic manager" to mean a
manager that Django creates for you -- either as a default manager on a model
with no managers, or to use temporarily when accessing related objects.
-Sometimes this default class won't be the right choice. One example is in the
-:mod:`django.contrib.gis` application that ships with Django itself. All ``gis``
-models must use a special manager class (:class:`~django.contrib.gis.db.models.GeoManager`)
-because they need a special queryset (:class:`~django.contrib.gis.db.models.GeoQuerySet`)
-to be used for interacting with the database. It turns out that models which require
-a special manager like this need to use the same manager class wherever an automatic
-manager is created.
+Sometimes this default class won't be the right choice. The default manager
+may not have all the methods you need to work with your data. A custom manager
+class of your own will allow you to create custom ``QuerySet`` objects to give
+you the information you need.
Django provides a way for custom manager developers to say that their manager
class should be used for automatic managers whenever it is the default manager
@@ -490,8 +487,7 @@ it will use :class:`django.db.models.Manager`.
Writing correct Managers for use in automatic Manager instances
---------------------------------------------------------------
-As already suggested by the :mod:`django.contrib.gis` example, above, the
-``use_for_related_fields`` feature is primarily for managers that need to
+The ``use_for_related_fields`` feature is primarily for managers that need to
return a custom ``QuerySet`` subclass. In providing this functionality in your
manager, there are a couple of things to remember.