#16505: Consider a different interface for get_next_by_FOO and
get_previous_by_FOO
-------------------------------------+-------------------------------------
Reporter: umbrae@… | Owner: nobody
Type: New | Status: new
feature | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design | Has patch: 0
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by umbrae@…):
In a perfect world, I'd rather there be only one way to do it, so I
suppose I'm proposing deprecating and eventually removing
Model.get_(next|prev)_by_FOO in favor of new queryset methods. In the near
term there could be overlap though, of course.
I know that's a long road and potentially a painful change for users for a
relatively small gain, so I'd leave that call up to you guys.
--
Ticket URL: <https://code.djangoproject.com/ticket/16505#comment:3>
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.
