diff options
| author | Jacob Kaplan-Moss <jacob@jacobian.org> | 2009-04-22 22:16:19 +0000 |
|---|---|---|
| committer | Jacob Kaplan-Moss <jacob@jacobian.org> | 2009-04-22 22:16:19 +0000 |
| commit | c00e8d20641910e0fdbce9f155e39b28bb824672 (patch) | |
| tree | a72a83ac9a6871fcc1a47f24cb63e00229536d64 /docs | |
| parent | d463580c1bbc17c6180d2f9638768769e850d8d0 (diff) | |
Added a `QuerySet.ordered` property to check if a queryset is already ordered. Refs #10163.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@10623 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/models/querysets.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index fa58060916..6c08fe079e 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -268,6 +268,12 @@ There's no way to specify whether ordering should be case sensitive. With respect to case-sensitivity, Django will order results however your database backend normally orders them. +.. versionadded:: 1.1 + +You can tell if a query is ordered or not by checking the +:attr:`QuerySet.ordered` attribute, which will be ``True`` if the +``QuerySet`` has been ordered in any way. + ``reverse()`` ~~~~~~~~~~~~~ |