#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 Rémy Hubscher):
1. How do we handle cases when the value in the database doesn't exists in
the callable iterator anymore.
- Let say you can select only a date during the next 7 days, how do
you update some other fields in the admin two weeks later?
2. What are the mandatory parameters that we need to provide to let the
callable be self sufficient on generating the callable?
- Probably the current instance? (We could handle a 7 days window
after the creation date of the object?)
Any thoughts about that?
--
Ticket URL: <https://code.djangoproject.com/ticket/28033#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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.1c25c3a28c7ff7a1011905419f95a1d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
