#27239: Unexpected behavior on get_FIELDNAME_display when as int as value
-------------------------------------+-------------------------------------
Reporter: levivm | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: choice, field | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => duplicate
Comment:
Duplicate of #20749 which suggests to add a system check to prohibit using
incorrect types in `choices`.
--
Ticket URL: <https://code.djangoproject.com/ticket/27239#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/064.9c40b465d1d80b1ba76bfb19b7e823cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
