#24342: Add EnumField model/form fields
-------------------------------------+-------------------------------------
Reporter: ovangle | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
The idea of a PostgreSQL-specific field was rejected on the mailing list
thread link in comment:6. Quoting Josh Smeaton:
I definitely do not like the idea of building a feature into
contrib.postgres that could be built for the rest of the database backends
too. It seems like a cop-out for doing less work, and really promotes one
built in backend above others. contrib.postgres should be a place for
postgres specific features, not for cutting out other backends.
--
Ticket URL: <https://code.djangoproject.com/ticket/24342#comment:11>
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/065.cb20d7743e2b71e3599654d8203e704e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
