#17813: Implement an opposite method for Entry.objects.latest
-------------------------------------+-------------------------------------
Reporter: tonnzor | Owner:
Type: New feature | Status: new
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Changes (by julien):
* needs_better_patch: 0 => 1
Comment:
Thanks for the patch. Like hcarvalhoalves, I think it would be non-DRY and
potentially confusing to allow for two attributes. `get_latest_by` is
sufficient to indicate which field should be used for ordering, so there
is no need for an extra attribute. Also, renaming `get_latest_by` would be
unnecessarily backwards-incompatible. So, all that's needed is a new
`earliest()` method that uses the inverse order.
--
Ticket URL: <https://code.djangoproject.com/ticket/17813#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
