#17813: Implement an opposite method for Entry.objects.latest
-------------------------------------+-------------------------------------
Reporter: tonnzor | Owner: Fandekasp
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 Fandekasp):
* needs_better_patch: 0 => 1
Comment:
You're right for first, I just went along with jimmysong implementation
without thinking about that. Will change that now
For the attributes, what is odd is to add a Meta.get_latest_by in your
model when you want to call a earliest(), don't you think ? It's also more
flexible to have 2 separate attributes, therefore I finally think it's the
best approach. And it doesn't break everybody's code.
--
Ticket URL: <https://code.djangoproject.com/ticket/17813#comment:8>
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.
