Document QuerySet.latest() behavior for null values
When sorting by date null values mean that date is unknown. Is there a reason to put them before any known date? Absence of date doesn't necessary mean an event will happen in the future, it means that the date is unknown. And word 'latest' suggests sorting by a known date.
Change History
(14)
| Component: |
Uncategorized → Documentation
|
| Summary: |
latest() QuerySet method should ignore null values → Document QuerySet.latest() behavior for null values
|
| Triage Stage: |
Unreviewed → Accepted
|
| Owner: |
changed from nobody to Parv Jain
|
| Status: |
new → assigned
|
| Owner: |
Parv Jain removed
|
| Status: |
assigned → new
|
| Owner: |
set to Chad Shrock
|
| Status: |
new → assigned
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
Django simply delegates to the database's ordering of null values. I'm not sure if Django should also add filtering to exclude null values -- that seems a bit magical to me. However, you could raise the idea on the DevelopersMailingList. For now, I'll accept the ticket as a documentation improvement.