Hi Adam, How about making the package official extension and bring under django org?
Thanks, Asif On Monday, May 8, 2017 at 9:22:04 PM UTC+6, Adam Johnson wrote: > > Update: I decided not to try merge django-mysql as django.contrib.mysql > because I think it's an advantage to have it as a separate package. As it > stands, it supports Django 1.8 to 1.11 for all features, so people who > aren't on cutting edge Django can still use all its features. Contrast that > with django.contrib.postgres, where new features are only available on > new Django versions, with their fixed release cycle. > > Sérgio, django-mysql already fully supports MySQL 5.7's JSON type with > its JSONField: > https://django-mysql.readthedocs.io/en/latest/model_fields/json_field.html > . Try that. > > On 4 May 2017 at 18:41, johannes mtwengi <johanne...@gmail.com > <javascript:>> wrote: > >> i would like to be part and start foundations coding giving back >> >> On Friday, March 4, 2016 at 1:09:00 AM UTC+2, Adam Johnson wrote: >>> >>> The *django.contrib.postgres* docs state: >>> >>> There is no fundamental reason why (for example) a contrib.mysql module >>>> does not exist >>> >>> >>> *Well...* over the past year and a bit I've been developing >>> Django-MySQL. It has a ton of features specific to MySQL and/or MariaDB. >>> For a quick tour of the features, see the exposition in the documentation: >>> https://django-mysql.readthedocs.org/en/latest/exposition.html (it's >>> not all suitable for Django core, some is kinda hacky (but well tested!)) >>> >>> At DUTH in November I talked with Josh Smeaton about posting a >>> suggestion here for *django.contrib.mysql*. Since then, I've simply >>> been lazy/forgetful, but now I'm here getting round to it. >>> >>> I'm also a bit motivated by my recent completion of its *JSONField* for >>> MySQL 5.7+ which is very similar to the *contrib.postgres* one, copying >>> and adapting large parts of code from Marc Tamlyn's work. We all know how >>> much everyone loves JSON these days. If anything, this could be a core >>> field rather than a *contrib* one - Oracle and SQLite also have JSON >>> capabilities now. JSON everywhere! >>> >>> Anyway... what's the interest in *django.contrib.mysql*? And where >>> woudl we go from here... >>> >> -- >> 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/sAgYOqBUvgI/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> django-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> 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/274f0162-f345-4946-ad56-328c20bdafff%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/274f0162-f345-4946-ad56-328c20bdafff%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Adam > -- 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/a296f932-9399-4907-92ed-8054215d087c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
