#26654: Better forms for django.contrib.postgres.fields
-------------------------------------+-------------------------------------
Reporter: primal100 | Owner: primal100
Type: New feature | Status: assigned
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by mjtamlyn):
Two main problems I have with this:
- That level of form declaration does not belong in the model. Even if we
have form fields capable of this, we should define them as form fields.
- These declarations imply to me a concrete specification of what your
data looks like. This begs the question - why would you use an HStore or a
JSON field in that case anyway?
--
Ticket URL: <https://code.djangoproject.com/ticket/26654#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/067.4dabb6c5903170caf495ca99ab91c310%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
