Browse files

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: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
ubernostrum committed Aug 15, 2008
1 parent 0c115f1 commit d8bfabe98d31299bfa24f71af47377495f360dae
Showing with 9 additions and 0 deletions.
  1. +9 −0 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).

0 comments on commit d8bfabe

Please sign in to comment.