#16760: ORM: Manager.latest() use pk by default
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
freek.wiekmeijer@… | Status: closed
Type: New | Component: Database layer
feature | (models, ORM)
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: wontfix | Has patch: 0
Triage Stage: Design | Needs tests: 0
decision needed | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by jacob):
* status: new => closed
* resolution: => wontfix
Comment:
I understand the use case here, but `latest` is specifically designed for
dates, not for primary keys. Remember: we can't guarantee that the PK is
in order, or even a number. Think, for example, about a model that uses
UUIDs for primary keys.
Thanks for the idea!
--
Ticket URL: <https://code.djangoproject.com/ticket/16760#comment:2>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.