Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.9.x] Fixed #26526 -- Documented QuerySet.latest()'s dependency on database ordering.

Browse Source 
Backport of e6c5e68acd4bff90e371fd148ed6976e147692ad from master
This commit is contained in:
Chad Shryock 2016-06-02 10:52:58 -07:00 committed by Tim Graham
parent 95ed1514f0
commit 9d52cdfbbc
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1954,6 +1954,17 @@ given parameters.
Note that ``earliest()`` and ``latest()`` exist purely for convenience and
readability.
.. admonition:: ``earliest()`` and ``latest()`` may return instances with null dates.
Since ordering is delegated to the database, results on fields that allow
null values may be ordered differently if you use different databases. For
example, PostgreSQL and MySQL sort null values as if they are higher than
non-null values, while SQLite does the opposite.
You may want to filter out null values::
Entry.objects.filter(pub_date__isnull=False).latest('pub_date')
``earliest()``
~~~~~~~~~~~~~~