From d8bfabe98d31299bfa24f71af47377495f360dae Mon Sep 17 00:00:00 2001 From: James Bennett Date: Fri, 15 Aug 2008 12:02:24 +0000 Subject: [PATCH] Fixed #8154: Added note to docs/db-api.txt indicating that reverse() is only useful when the QuerySet has some prior ordering git-svn-id: http://code.djangoproject.com/svn/django/trunk@8371 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/db-api.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/db-api.txt b/docs/db-api.txt index ca7d47f8fa..61afb14770 100644 --- a/docs/db-api.txt +++ b/docs/db-api.txt @@ -621,6 +621,15 @@ penultimate item and so on. If we had a Python sequence and looked at that mode of access (slicing from the end), because it's not possible to do it efficiently in SQL. +Also, note that ``reverse()`` should generally only be called on a +``QuerySet`` which has a defined ordering (e.g., when querying against +a model which defines a default ordering, or when using +``order_by()``). If no such ordering is defined for a given +``QuerySet``, calling ``reverse()`` on it has no real effect (the +ordering was undefined prior to calling ``reverse()``, and will remain +undefined afterward). + + ``distinct()`` ~~~~~~~~~~~~~~