#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 anonymous):
Replying to [comment:21 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.
You cannot say that generally. The answer is as always, it depends. There
are perfectly valid uses of this, for example, storing a little (dynamic)
metadata without setting up a NoSQL database.
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:28>
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 [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.
