From 11b7680d0e640a7d4b1c942f74e9197b6ec924b1 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 12 Nov 2014 22:00:48 +0100 Subject: [PATCH] Fixed #23774 -- Clarified QuerySet.order_by() and related models. --- docs/ref/models/querysets.txt | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 77f933de6a..218a4ff35f 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -289,9 +289,10 @@ and so on for as many models as you want to join. For example:: Entry.objects.order_by('blog__name', 'headline') If you try to order by a field that is a relation to another model, Django will -use the default ordering on the related model (or order by the related model's +use the default ordering on the related model, or order by the related model's primary key if there is no :attr:`Meta.ordering -` specified. For example:: +` specified. For example, since the ``Blog`` +model has no default ordering specified:: Entry.objects.order_by('blog') @@ -299,7 +300,10 @@ primary key if there is no :attr:`Meta.ordering Entry.objects.order_by('blog__id') -...since the ``Blog`` model has no default ordering specified. +If ``Blog`` had ``ordering = ['name']``, then the first queryset would be +identical to:: + + Entry.objects.order_by('blog__name') .. versionadded:: 1.7