From e3cf8d2e94fe5f0b6d41774edbab0a9800b397ff Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Wed, 6 Sep 2017 19:21:38 -0400
Subject: [PATCH] [1.8.x] Fixed #28561 -- Removed inaccurate docs about
QuerySet.order_by() and joins.
As of ccbba98131ace3beb43790c65e8f4eee94e9631c, both examples don't use
a join.
Backport of 44a6c27fd461e1d2f37388c26c629f8f170e8722 from master
---
docs/ref/models/querysets.txt | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 9d45f0193f..c0500b1b1a 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -320,20 +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')
-
-.. versionadded:: 1.7
-
- The ability to order a queryset by a related field, without incurring
- the cost of a JOIN was added.
-
You can also order by :doc:`query expressions </ref/models/expressions>` by
calling ``asc()`` or ``desc()`` on the expression::