I agree regarding choosing the most most useful bits. When we discussed this at DUTH I did mention that there were some features that would be very difficult to get included in Django. I guess you'd have to consider whether or not you'd be willing to move features from django-mysql into contrib and how that might affect django-mysql in the longer term. I really like the idea of having a contrib.mysql though, as it shows we're not just committed to moving postgres forward. Having a voice for mysql in the team would also be very helpful.
Cheers On Friday, 4 March 2016 18:15:15 UTC+11, Aymeric Augustin wrote: > > Hi Adam, > > django-mysql has a rather large API surface. I think the first step would > be to make a list of the most stable and generally useful bits that are > candidate for inclusion in Django and to write that list down in a DEP. > > The fields, functions, lookups, and aggregates are good candidates. I’m > less sure about the QuerySet extensions because we don’t have anything > similar yet. We’d have to think about the implications. > > Looking forwards, django-mysql could be an experimental ground for > features. When they stabilize, the most common features could go into > django.contrib.mysql. > > Since making changes to public APIs is a pain, you only want to put code > in Django when it’s done. To a lesser extent, we have Python’s “standard > library is where modules go to die” problem. > > It would obviously help if other community members expressed interest in > django.contrib.mysql or, even better, intent to help maintain it in the > future. > > I hope this helps, > > -- > Aymeric. > > PS: if this plan comes to fruition, most likely you’ll get commit access > along the way ;-) > > > On 04 Mar 2016, at 00:09, Adam Johnson <djch...@gmail.com <javascript:>> > 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 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-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/ed9245ea-f908-4c1c-91ad-cb94f0147959%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/ed9245ea-f908-4c1c-91ad-cb94f0147959%40googlegroups.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 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/562f8c3e-4bf1-47cf-9a98-1a6f9b171528%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
