#30095: System check error for tuples in model field choices
-------------------------------------+-------------------------------------
Reporter: msart | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: choices tuple | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* component: Uncategorized => Database layer (models, ORM)
Comment:
I think you could solve your issue and improve your code by using
`NumericRange` in your choices instead of tuples. Now there may be other
custom fields that want to use tuples for choice values, but perhaps we
should address that if/when someone presents a use case.
--
Ticket URL: <https://code.djangoproject.com/ticket/30095#comment:1>
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/063.7ed96a819c7c628586cff9b0248bba6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
