Hey again, sorry, I just found https://github.com/django/django/pull/11452 . So I guess I'll wait for Django 3.1 in August 2020.
Best, Johannes On Sat, Oct 19, 2019 at 9:22 AM Johannes Wilm <johannesw...@gmail.com> wrote: > Hey, > I noticed that there is no news concerning a standard json field in the > 3.0 release notes. What would the most future-proof way be of incorporating > a json field currently? Should one use django-jsonfallback and hope it will > eventually land in mainline django or is that just meant as a proof of > concept? > > Best, > Johannes > > > On Saturday, October 20, 2018 at 6:14:39 AM UTC+2, Raphael Michel wrote: >> >> Hi everyone, >> >> I used the sprints at DjangoCon US to work on this issue in form of a >> third-party package. Mainly, I created a subclass of >> django.contrib.postgres.fields.JSONField that >> >> - includes code from django-mysql to work on MySQL 5.7+ as well >> - does some nasty hacks to even work on MariaDB 10.2.7+ >> - gracefully falls back to storing JSON strings in a TextField on all >> other databases >> >> Unfortunately, the differences between the JSON implementations >> (especially between MariaDB and MySQL) seem to be quite large. Since my >> primary objective was to prove that it is possible to create a >> multi-database field, I resolved this mostly with some back-and-forth data >> conversion hacks, instead of searching for a clean solution. Not all >> features of the PostgreSQL version are possible on MySQL/MariaDB, but the >> most useful ones all are. >> >> This would probably need a lot of cleaning up before considering to move >> it to Django core, and you'd likely also want to explore integrating >> Oracle/SQLite for that. I will probably not have time to do that, but if >> someone else wants to, this might provide a starting point. >> >> Here's the repository: https://github.com/raphaelm/django-jsonfallback >> >> Best >> Raphael >> >> P.S. Thanks to all organizers and attendees for an amazing conference <3 >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/zfred27yVPg/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/628a4227-32b9-4e1e-8d1e-5f8a75cc31cf%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/628a4227-32b9-4e1e-8d1e-5f8a75cc31cf%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Johannes Wilm -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABkgm-Q4aHg4TY5%3D9WpUQuRFB6GKzXRta39xHiPDyCCbZFCfjg%40mail.gmail.com.
