Re: [Django] #11557: get_latest_by should support multiple columns via tuple like ordering

[Django]

#11557: get_latest_by should support multiple columns via tuple like ordering
-------------------------------------+-------------------------------------
Reporter: forest | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.0
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: get_latest_by | Needs documentation: 0
ordering | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by denilsonsa):

* cc: denilsonsa@… (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/11557#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#11557: get_latest_by should support multiple columns via tuple like ordering
-------------------------------------+-------------------------------------

Reporter: Forest Bond | Owner: François
| Freitag
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Changes (by François Freitag):

* owner: nobody => François Freitag
* needs_better_patch: 1 => 0
* version: 1.0 => master
* status: new => assigned

Comment:

[https://github.com/django/django/pull/8668 PR]

--
Ticket URL: <https://code.djangoproject.com/ticket/11557#comment:10>

[Django]

#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
-------------------------------------+-------------------------------------

Changes (by Tim Graham <timograham@…>):

* status: assigned => closed
* resolution: => fixed

Comment:

In [changeset:"ad4a8acdb55a80a6a6dec60724b22abed0025399" ad4a8ac]:
{{{
#!CommitTicketReference repository=""
revision="ad4a8acdb55a80a6a6dec60724b22abed0025399"
Fixed #11557 -- Added support for a list of fields in Meta.get_latest_by
and QuerySet.earliest()/latest().
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/11557#comment:11>

[Django]

#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>