Commit c0181f2c authored by Tim Graham's avatar Tim Graham
Browse files

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

Thanks Simon Charette for review.
parent 4e2da368
Loading
Loading
Loading
Loading
+6 −0
Original line number Diff line number Diff line
@@ -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 −0
Original line number Diff line number Diff line
@@ -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()``
~~~~~~~~~~~~~