test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #26310 -- Documented that a queryset ordering must be specified to ensure ordered results. 

Thanks Simon Charette for review.
This commit is contained in:
Tim Graham 2016-03-03 10:15:24 -05:00
parent 4e2da368db
commit c0181f2c1f
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ref/models/options.txt
View File

@ -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``
---------------

6
docs/ref/models/querysets.txt
View File

@ -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()``
~~~~~~~~~~~~~