#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 russellm):
For the record - I'm -0 on this. For my money, if you're putting JSON in a
database field (and expecting it to be searchable etc), you're doing it
wrong. I won't stand in the way if someone else in the core team feels
particularly enthused, but I'm not rushing myself.
Also, the previous argument about XMLField has been rendered invalid -- we
removed XMLField in 1.3.
--
Ticket URL: <http://code.djangoproject.com/ticket/12990#comment:21>
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.
