#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 russellm):
If you're arguing for JSONField as a way of avoiding setting up a NoSQL
store, then you've just proved my point. If you need a non-relational
store, *use a non-relational store*. Yes, there may be reasons why this
isn't possible for political or business reasons, but that doesn't change
the fact that:
* There is a better way to solve the problem
* Django shouldn't be encouraging people to hack around the root cause of
problems
* The absence of a JSONField in Django core doesn't prevent the community
from developing a canonical implementation that can be used as a third-
party library.
* Putting JSONField in core wouldn't affect the stability or reliability
of that third party implementation -- it just means the core team are the
only people who can maintain it.
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:29>
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.
