From 593810a5014ecaa28215839fb42f03df44a069d0 Mon Sep 17 00:00:00 2001 From: Jacob Kaplan-Moss Date: Tue, 5 Aug 2008 16:13:28 +0000 Subject: Fixed #7904: added support for a "use_for_related_fields" property on managers. If True, the manager will be used for related object lookups instead of the "bare" QuerySet introduced bu [8107]. Patch from Justin Bronn. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8212 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/model-api.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs') diff --git a/docs/model-api.txt b/docs/model-api.txt index f624e68844..b6a446b50e 100644 --- a/docs/model-api.txt +++ b/docs/model-api.txt @@ -1507,6 +1507,17 @@ 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. +Using managers for related object access +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +By default, Django uses a "bare" (i.e. default) manager when accessing related +objects (i.e. ``choice.poll``). If this default isn't appropriate for your default manager, you can force Django to use a custom manager for related object attributes by giving it a ``use_for_related_fields`` property:: + + class MyManager(models.Manager):: + use_for_related_fields = True + + ... + Model methods ============= -- cgit v1.3