#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 Marco Silva):
Would a outsourced list, (eg. from an api with a list of car brands or
person names) be a good use case to change the choice fields dynamicly?
I think the main problem here is what to do with stored data that is
currently "invalid"(present in the database but not in the returned list
from the callable), currently admin forms ignore it as if it was null
--
Ticket URL: <https://code.djangoproject.com/ticket/28033#comment:7>
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.c2bca01c5404c5de500653cbfdd660a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
