#11557: get_latest_by should support multiple columns via tuple like ordering
-------------------------------------+-------------------------------------
Reporter: Forest Bond | Owner: François
| Freitag
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: get_latest_by | Triage Stage: Accepted
ordering |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"1fecde6be9f42050ab993ecc293169280df3a974" 1fecde6]:
{{{
#!CommitTicketReference repository=""
revision="1fecde6be9f42050ab993ecc293169280df3a974"
Refs #11557 -- Removed the field_name keyword argument to
QuerySet.earliest() and latest().
Per deprecation timeline.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/11557#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.9c92c5da06d7a4ee0f62ac1364f62f3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
