From 459c71e3320b17bb4e0f3188baf7ca3ff1bd2260 Mon Sep 17 00:00:00 2001 From: Justin Bronn Date: Fri, 26 Mar 2010 20:14:53 +0000 Subject: Fixed #12930, #12832, #11538 -- Refactored and merged the GeoDjango documentation into the rest of the Django docs. git-svn-id: http://code.djangoproject.com/svn/django/trunk@12856 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/db/managers.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/topics/db') diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt index d7f5569c91..4569775652 100644 --- a/docs/topics/db/managers.txt +++ b/docs/topics/db/managers.txt @@ -296,11 +296,12 @@ 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 -`django.contrib.gis` application that ships with Django itself. All `gis` -models must use a special manager class (``GeoManager``) because they need a -special queryset (``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. +: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. 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 -- cgit v1.3