#27239: Unexpected behavior on get_FIELDNAME_display when as int as value
-------------------------------------+-------------------------------------
Reporter: levivm | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by levivm):
Replying to [comment:1 claudep]:
> Why would you use integer values for a CharField in the first place?
Because it's possible. If Django allows you to assign it, so, it should
take care of that case.
--
Ticket URL: <https://code.djangoproject.com/ticket/27239#comment:2>
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/064.1d46583f1708eee3b17858cfa17308e2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
