[1.10.x] Fixed #26526 -- Documented QuerySet.latest()'s dependency on database ordering.
Backport of e6c5e68acd
from master
This commit is contained in:
parent
3eb31867bb
commit
cd4246aab1
|
@ -1956,6 +1956,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()``
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
|
|
Loading…
Reference in New Issue