#12990: New Field Type: JSONField
-------------------------------------+-------------------------------------
Reporter: paltman | Owner: nobody
Type: New | Status: new
feature | Component: Database layer
Milestone: | (models, ORM)
Version: 1.2-beta | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design | Has patch: 1
decision needed | Needs tests: 1
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 1 |
-------------------------------------+-------------------------------------
Changes (by ShawnMilo):
* cc: ShawnMilo (added)
Comment:
I'd like to see this as well, because we use a JSON field frequently. I
think the argument against that searching JSON in a queryset is poor
design is a straw-man argument. I haven't heard anyone ask for a JSON
field with this in mind. It's just convenient to store serialized data to
avoid unnecessary auxiliary storage and proliferation of extra fields and
models.
Having a canonical JSON field is better than people implementing their
own, in my opinion, because it makes it provides consistency across
projects without needing to copy/paste code into each no project.
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:25>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
