#26141: __lt__ for model instances
-------------------------------------+-------------------------------------
Reporter: srkunze | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
My initial inclination is that it's better to leave this up to each
project to implement as needed, as a sensible default may not be so clear.
See #22843 for some related discussion. I guess it's worth raising on the
DevelopersMailingList -- if you can get a consensus there on how to
proceed with the implementation, then let's reopen this.
As a side note, the implementation above assumes the two objects are the
same type, or at least that they both have fields with the name as what's
in the first models `Meta.ordering`.
--
Ticket URL: <https://code.djangoproject.com/ticket/26141#comment:1>
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/065.37f372c691bd1416c712a0898aaa8006%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
