Agreed, as other databases catch up with the feature set offered in contrib.postgres I think moving this field into core is likely - it's a field that a number of databases are working on adding. It's worth noting that the PG implementation is 9.4+ only, the 9.2/9.3 implementation of json should not be used.
There are many suitable third party apps which do a simple dumps/loads around a text blob. There isn't really any benefit in adding this to core in my opinion. On 7 July 2015 at 15:38, Michael Manfre <[email protected]> wrote: > The django-contrib-postgres JSONField takes advantage of JSON being a > native type that allows it's data fields to be used by the ORM, instead of > just a text field that wraps json.dumps() and json.loads(). All of the core > supported backends seem to have some flavor of native JSON support (MS SQL > is adding native JSON in SQL Server 2016). I haven't investigated whether > or not they could be sanely implemented as a common field. That might be a > worthwhile change to target for Django 1.10, guarded by a DatabaseFeature > for all of the earlier versions of each database that don't support it. > > Regards, > Michael Manfre > > > On Tue, Jul 7, 2015 at 9:57 AM, <[email protected]> wrote: > >> >> Hi all, >> >> I'd like to know why this feature will be only available on postgres and >> not as a Field for any database, like this product? This Field would be >> very usefull for many users I think. >> >> https://github.com/bradjasper/django-jsonfield >> >> >> https://docs.djangoproject.com/en/dev/releases/1.9/#django-contrib-postgres >> >> By. >> >> Enviado via UCSMail. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/0459e983-7098-475c-9e3f-14a076513f4a%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/0459e983-7098-475c-9e3f-14a076513f4a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > GPG Fingerprint: 74DE D158 BAD0 EDF8 > keybase.io/manfre > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAGdCwBtTHj6dVgnUO2z_jojwRBMYwZT5YGWQxTdf1%2B7X3yBTmA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAGdCwBtTHj6dVgnUO2z_jojwRBMYwZT5YGWQxTdf1%2B7X3yBTmA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1FtEpseeOOJsAob9t-nA6okRVj3J8uBXD%2BnB26QABdL2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
