Current maintainer of https://github.com/bradjasper/django-jsonfield here and I would definitely support this.
-Brad On Thu, Jun 23, 2016 at 9:28 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hello, > > On 23 Jun 2016, at 15:40, Tim Graham <timogra...@gmail.com> wrote: > > Marc said, "I'm happy for JSONField to be made a core field on the > condition that it's underlying support is more than a text blob on all our > main databases. It sounds like this will soon be the case.” > > > In order to discourage people from using JSONField on databases where it > cannot be implemented efficiently i.e. not with a text blob, the best > solution may be to add it to Django and raise a warning when it’s misused. > > I’m not sure we can do that with a check, though, as we can’t introspect > database routing logic (without adding a disproportionate amount of > complexity). It would have to be a runtime warning. > > -- > Aymeric. > > -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAAmjBRJKDDT%2BAdDhbGqATChS%2BF6POK9X0fcQmQFNq33Zc7c29A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
