#15319: _get_next_or_previous_by_FIELD populated from Meta
--------------------------------------------------------+-------------------
Reporter: alexr | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Triage Stage: Design decision needed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
--------------------------------------------------------+-------------------
Comment (by alexr):
Yeah, I'd be just as happy if I were able to specify seekable (or whatever
if gets called in the end) on the fields.
We'd also need to check that it wasn't set for a field that was the
primary key. (That would have been an issue in my original proposal too.)
I think the lookup adds some pk fallback code that might get weird if it
was already seeking by pk.
--
Ticket URL: <http://code.djangoproject.com/ticket/15319#comment:3>
Django <http://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.
