From c0181f2c1f982d27cdcea2ed293aa34a3ecf7d8b Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 3 Mar 2016 10:15:24 -0500 Subject: [PATCH] Fixed #26310 -- Documented that a queryset ordering must be specified to ensure ordered results. Thanks Simon Charette for review. --- docs/ref/models/options.txt | 6 ++++++ docs/ref/models/querysets.txt | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt index 8fbf4b219e..e047a01f10 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -288,6 +288,12 @@ Django quotes column and table names behind the scenes. incurs a cost to your database. Each foreign key you add will implicitly include all of its default orderings as well. + If a query doesn't have an ordering specified, results are returned from + the database in an unspecified order. A particular ordering is guaranteed + only when ordering by a set of fields that uniquely identify each object in + the results. For example, if a ``name`` field isn't unique, ordering by it + won't guarantee objects with the same name always appear in the same order. + ``permissions`` --------------- diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index b632434456..d60b3a5866 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -387,6 +387,12 @@ query will be ordered by ``pub_date`` and not ``headline``:: incurs a cost to your database. Each foreign key you add will implicitly include all of its default orderings as well. + If a query doesn't have an ordering specified, results are returned from + the database in an unspecified order. A particular ordering is guaranteed + only when ordering by a set of fields that uniquely identify each object in + the results. For example, if a ``name`` field isn't unique, ordering by it + won't guarantee objects with the same name always appear in the same order. + ``reverse()`` ~~~~~~~~~~~~~