#12990: New Field Type: JSONField
-------------------------------------+-------------------------------------
Reporter: paltman | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.2-alpha
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
For the record I think there are many valid use cases for storing JSON in
the database. Also, PostgreSQL 9.2 already has JSON typed field, 9.3 might
make it nicely searchable. If the JSON improvements get into 9.3 then it
would actually be a better solution than HStore.
But, we likely don't want this field in core. If we are restricted to the
functionality offered by all databases, then it basically boils down to
"convert to text on save, convert to python on load". Which isn't all that
great.
My vote is on improving core support for custom fields. If one can write a
json field that just works outside of core, then "pip install django-
jsonfield" seems like a good way to add this feature...
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:42>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
