p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #2609 -- Improved docs/sites.txt CurrentSiteManager to explain gotcha with models.Manager 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3686 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-08-31 04:08:25 +00:00
parent 5e69536f7c
commit 452847a659
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/sites.txt
View File

@ -266,7 +266,18 @@ this::
If you attempt to use ``CurrentSiteManager`` and pass a field name that doesn't
exist, Django will raise a ``ValueError``.
Finally, note that you'll probably want to keep a normal (non-site-specific)
``Manager`` on your model, even if you use ``CurrentSiteManager``. As explained
in the `manager documentation`_, if you define a manager manually, then Django
won't create the automatic ``objects = models.Manager()`` manager for you.
Also, note that certain parts of Django -- namely, the Django admin site and
generic views -- use whichever manager is defined *first* in the model, so if
you want your admin site to have access to all objects (not just site-specific
ones), put ``objects = models.Manager()`` in your model, before you define
``CurrentSiteManager``.
.. _manager: http://www.djangoproject.com/documentation/model_api/#managers
.. _manager documentation: http://www.djangoproject.com/documentation/model_api/#managers
How Django uses the sites framework
===================================