#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 aaugustin):
I've recently rolled my own implementation of this.
I use it in a logging table where I want to store an event_kind (ex :
"USER_LOGIN") + a datetime + a bunch of parameters (ex : username, remote
IP) that depend on the kind of event. I want to be able to add arbitrary
parameters at any point. Normalizing parameters in a separate table (e.g.
storing event_id, key, value in another table for each parameter) seems
overkill — I don't want to add a model just for this.
So I think there are some real-life use cases for storing a JSON-
serialized dict in a database field. Since it's moderately difficult to
get right, +0 for adding it in Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:32>
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.
