mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-11-03 13:23:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fixed #11039: documented that aggregation and generic relations don't mix. Thanks, psmith.

Browse source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@10781 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jacob Kaplan-Moss 2009-05-14 02:38:27 +00:00
parent 5bdee2556e
commit d987b378ce
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/ref/contrib/contenttypes.txt
View file

@ -339,6 +339,21 @@ pointing at it will be deleted as well. In the example above, this means that
if a ``Bookmark`` object were deleted, any ``TaggedItem`` objects pointing at if a ``Bookmark`` object were deleted, any ``TaggedItem`` objects pointing at
it would be deleted at the same time. it would be deleted at the same time.
Generic relations and aggregation
---------------------------------
:ref:`Django's database aggregation API <topics-db-aggregation`
doesn't work with a
:class:`~django.contrib.contenttypes.generic.GenericRelation`. For example, you
might be tempted to try something like::
Bookmark.objects.aggregate(Count('tags'))
This will not work correctly, however. The generic relation adds extra filters
to the queryset to ensure the correct content type, but the ``aggregate`` method
doesn't take them into account. For now, if you need aggregates on generic
relations, you'll need to calculate them without using the aggregation API.
Generic relations in forms and admin Generic relations in forms and admin
------------------------------------ ------------------------------------