#12990: New Field Type: JSONField
---------------------------------------------------+------------------------
Reporter: paltman | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2-beta
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by Alex):
Replying to [comment:2 floguy]:
> +1 on this. There are many implementations of this floating around, and
most of them are wrong. It's a common-enough pattern that Django should
provide the canonical implementation.
How are most of them wrong? It's pretty trivial (there's actually an
implementation in the tests).
Replying to [comment:3 marcelor]:
> +1 If XMLField is in the core then JSONField deserves to be in too. Also
I'm tempted to propose the removal of XMLField, you all know that
> the use of XML as a format to store arbitrary data has dramatically
decreased in favour of JSON.
XMLField at this point does almost nothing (doesn't even do validation at
this point).
--
Ticket URL: <http://code.djangoproject.com/ticket/12990#comment:4>
Django <http://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.
