#13035: Wrong documentaion or bad admin behaviour
----------------------------------------+-----------------------------------
Reporter: rasca | Owner: nobody
Status: new | Milestone: 1.2
Component: django.contrib.admin | Version: SVN
Keywords: manager objects admin docs | Stage: Unreviewed
Has_patch: 0 |
----------------------------------------+-----------------------------------
When creating custom models managers the docs say:
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.
So if in a model I have
{{{
new = NewManager()
objects = models.Manager()
}}}
the admin should work as if there isn't any NewManager but it doesn't
The following works as desired:
{{{
objects = models.Manager()
new = NewManager()
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/13035>
Django <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.
