summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2015-03-13 15:40:25 -0400
committerTim Graham <timograham@gmail.com>2015-03-13 15:40:25 -0400
commitb9d9ab23bdcc404708aada664e718a9d56415ca3 (patch)
treeee7ca46cb018dc47c309874a122bd6783124265f
parente8a758e941bb36f69b6224b73b00b9d6a814bbdc (diff)
Refs #24462 -- Emphasized that order_by() clears previous ordering.
-rw-r--r--docs/ref/models/querysets.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 05de43fa1f..fdaa79540a 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -388,6 +388,11 @@ You can tell if a query is ordered or not by checking the
:attr:`.QuerySet.ordered` attribute, which will be ``True`` if the
``QuerySet`` has been ordered in any way.
+Each ``order_by()`` call will clear any previous ordering. For example, this
+query will be ordered by ``pub_date`` and not ``headline``::
+
+ Entry.objects.order_by('headline').order_by('pub_date')
+
.. warning::
Ordering is not a free operation. Each field you add to the ordering