#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 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by Lee S):
I would love to see a canonical version of JSON fields included.
I routinely find storing non-structured, non-searchable data in the
database to be extremely useful in many use cases. Setting up a NoSQL
database is often overkill. The real need is to store the odd JSON field
in an otherwise traditional SQL model. The example cited above, storing
flexible metadata is a common one -- for example, key/value pairs
indicating user preferences.
I'm at the point where I have to try one of the many implementations
listed above and cross my fingers that it's not broken.
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:31>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
