#35566: Support get_FOO_display() on GeneratedField
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
roniemartinez |
Type: New | Status: new
feature |
Component: Database | Version: 5.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Please add support for get_FOO_display() on GeneratedField.
We initially used a normal IntegerField with choices
[IntegerField(choices=choices, ...)] and then running a SQL to make this
field a generated field. We then migrated to GeneratedField while
maintaining the output_field similar to our old one.
However, we found that get_FOO_display() don't work anymore and we had to
write a method for this, instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/35566>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701905ec1e4a0-03988482-ae33-4a45-9320-b1d42b9a610a-000000%40eu-central-1.amazonses.com.
