#12990: New Field Type: JSONField
-------------------------------------+-------------------------------------
Reporter: paltman | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.2-alpha
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by lukeplant):
The WONTFIX will remain unless you bring this up on Django-devs.
However, one further reason why it is a bad idea is the existence of
hstore in Postgres.
This is a database specific solution, and is a much better solution than
storing JSON in a text field for many applications. Providing a built-in
JSONField discourages people from finding better solutions.
Also Googling "django JSONField" gives you several solutions that are
easily installable using PyPI, and work fine for most people, so I don't
see how it is an issue. It's extremely easy to get hold of a working
JSONField if you want one.
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:41>
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 https://groups.google.com/groups/opt_out.
