summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2017-09-06 19:21:38 -0400
committerTim Graham <timograham@gmail.com>2017-09-06 19:32:42 -0400
commit3df8ccf6fc3fa0ab2acf9a03da43fea87f8ff392 (patch)
tree46548cbc6584a6f3aa499b1285eadd352604009d
parent89cb0a451c9cb01ace7e996231c8991dc6637419 (diff)
downloaddjango-stable/1.9.x.tar.gz
[1.9.x] Fixed #28561 -- Removed inaccurate docs about QuerySet.order_by() and joins.stable/1.9.x
As of ccbba98131ace3beb43790c65e8f4eee94e9631c, both examples don't use a join. Backport of 44a6c27fd461e1d2f37388c26c629f8f170e8722 from master
-rw-r--r--docs/ref/models/querysets.txt9
1 files changed, 0 insertions, 9 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 5834e3d3e2..6bf37bc72b 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -320,15 +320,6 @@ identical to::
Entry.objects.order_by('blog__name')
-It is also possible to order a queryset by a related field, without incurring
-the cost of a JOIN, by referring to the ``_id`` of the related field::
-
- # No Join
- Entry.objects.order_by('blog_id')
-
- # Join
- Entry.objects.order_by('blog__id')
-
You can also order by :doc:`query expressions </ref/models/expressions>` by
calling ``asc()`` or ``desc()`` on the expression::