mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-03 18:38:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Merge pull request #1245 from oinopion/list_select_related

Browse source 
Fixed #19080 -- Fine-grained control over select_related in admin
This commit is contained in:
Marc Tamlyn 2013-06-06 01:27:05 -07:00
commit 9ed971f4f1
6 changed files with 88 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

22
docs/ref/contrib/admin/index.txt
View file

@ -812,12 +812,24 @@ subclass::
the list of objects on the admin change list page. This can save you a
bunch of database queries.
The value should be either ``True`` or ``False``. Default is ``False``.
.. versionchanged:: dev
Note that Django will use
:meth:`~django.db.models.query.QuerySet.select_related`,
regardless of this setting if one of the ``list_display`` fields is a
``ForeignKey``.
The value should be either a boolean, a list or a tuple. Default is
``False``.
When value is ``True``, ``select_related()`` will always be called. When
value is set to ``False``, Django will look at ``list_display`` and call
``select_related()`` if any ``ForeignKey`` is present.
If you need more fine-grained control, use a tuple (or list) as value for
``list_select_related``. Empty tuple will prevent Django from calling
``select_related`` at all. Any other tuple will be passed directly to
``select_related`` as parameters. For example::
class ArticleAdmin(admin.ModelAdmin):
list_select_related = ('author', 'category')
will call ``select_related('author', 'category')``.
.. attribute:: ModelAdmin.ordering