#3416: Model API documentation section 'Modifying initial Manager QuerySets'
misleads about Admin behaviour
-----------------------+----------------------------------------------------
Reporter: Alex Dedul | Owner: jacob
Status: new | Component: Documentation
Version: SVN | Keywords:
Stage: Unreviewed | Has_patch: 0
-----------------------+----------------------------------------------------
It says:
{{{
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.
}}}
But if you have your custom manager in a model even called 'objects' admin
anyway will display all records from model regardless specified custom
manager. The only way i found to tell admin to use custom manager is to
use 'manager' attribute in inner Admin class in a model. So i guess
reference to admin should be removed from here for now and 'manager'
attribute of inner Admin class documented instead.
--
Ticket URL: <http://code.djangoproject.com/ticket/3416>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
