#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
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
This idea was discussed and vetoed by one of our BDFLs on #django-social.
Here are the relevant logs, edited for readability.
> 2012-01-20 21:18:10 <jacobkm> (...) we've explicitly decided *not* to
include (...) JSONField
> 2012-01-20 21:21:58 <jacobkm> (...) I'm not saying there's no good
reason for it, I'm saying the bad reasons outweigh the good and that's why
it shouldn't ship with Django.
> 2012-01-20 21:22:11 <jacobkm> Under the Don't Give Users Loaded Guns
Aimed At Feet principle.
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:39>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
