#26654: Better forms for django.contrib.postgres.fields
-------------------------------------+-------------------------------------
Reporter: primal100 | Owner: primal100
Type: New feature | Status: closed
Component: contrib.postgres | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: postgres, array, | Triage Stage:
hstore, json, forms | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: assigned => closed
* resolution: => needsinfo
Comment:
I raised similar concerns on the [https://groups.google.com/d/topic
/django-developers/BByaPG39iw8/discussion django-developers thread]. I
think we also need separate tickets for each enhancement (if the
discussion yields consensus to move forward with any of the proposals)
rather than a single ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/26654#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 [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/067.04bd4291464dc92d86fdd098000f4828%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
