#25995: Support serialization to `django.contrib.postgres.fields.jsonb.py`
----------------------------------+--------------------------------------
Reporter: jimgraham | Owner: nobody
Type: New feature | Status: new
Component: contrib.postgres | Version: 1.9
Severity: Normal | Resolution:
Keywords: JSONB | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by mjtamlyn):
Such a field would actually be quite different in implementation to the
current field. We currently lever psycopg2's serialization and while this
can be customised[1], it is most easily customisable at the field level.
There is a possibility of providing an alternative to `Json()` for
adaption (into the db), but coming back out can only be done at the
connection level.
A JSON field which does all of its de-/serialization in the field would be
possible of course, one such implementation is
https://github.com/bradjasper/django-jsonfield/
[1] http://initd.org/psycopg/docs/extras.html#json-adaptation
--
Ticket URL: <https://code.djangoproject.com/ticket/25995#comment:4>
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.cc18e7f838951429e0d18e9f41a5083e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
