#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 anonymous):
How disappointing. In my case, I want to store user-specific settings
provided by the UI guys which are used purely for layout, styles, etc... I
don't want to have to maintain normalised tables for a constantly-updating
data structure which is only ever stored/retrieved as a whole.
I keep finding this in Django (and Python in general) - great ideas get
vetoed because "we don't dare trust a developer to use tools properly".
--
Ticket URL: <https://code.djangoproject.com/ticket/12990#comment:43>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
