#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 |
-------------------------------------+-------------------------------------
Comment (by sorl):
I think the usecase for something like this should be simply serialized
data in a field, not searchable and not just a mapping to a dict. Given
that, we might as well use pickle, but then we might loose data
portability. If you want to build an efficient relational db centric
application you probably want to use something like this and I think many
people realize that but the many implementations floating around makes it
hard for them to decide which one to use. If Django wants to advocate for
that kind of database design then perhaps it is a good idea to include a
serialization field. I have a very simple lazier approach, it can't
serialize strings but it only deserializes on attr access,
https://github.com/aino/django-cerial/blob/master/cerial/fields.py
--
Ticket URL: <http://code.djangoproject.com/ticket/12990#comment:23>
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.
