#28033: Allow passing choices as a callable in a model field
-------------------------------------+-------------------------------------
Reporter: Ian Foote | Owner: Rémy
| Hubscher
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: choices | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Elena Neacsu):
As I understand, the only cases when we would need this as a callable is
when we would like to have something like this:
CHOOSE_DATE = [
("2017-04-05", "Yesterday"),
("2017-04-06", "Today"),
("2017-04-07", "Tomorrow"),
]
The dates should be updated every day to reflect the reality. So, it
concerns only the date/time, in other cases (e.g. categories or types) we
could just use a ForeignKey.
Could you confirm or provide some other cases?
--
Ticket URL: <https://code.djangoproject.com/ticket/28033#comment:5>
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/067.a37da29ff11d4f13e28f1c6d4d19540f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
