#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 |
--------------------------------------------------------+-------------------
Changes (by russellm):
* stage: Unreviewed => Design decision needed
Comment:
I accept the broad principle that it should be easier to easily add
"get_X_by_Y" style fields for any field type, not just date fields.
However, my inclination isn't to take this away from individual fields,
but to add this as an extra feature for fields -- i.e., for me, this ins't
a model-level issue, it's a field configuration issue, and you should be
able to say {{{ last_name = models.CharField(max_length=255,
seekable=True) }}} (bikeshedding the attribute name), false by default for
most fields, but True by default for DateFields et al.
--
Ticket URL: <http://code.djangoproject.com/ticket/15319#comment:2>
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.
