Nice work, Adam. What's your main motivation for wanting to include it in 
Django itself? Do you think that including it will simplify the code much? 
Do you hope to attract new contributors by including it in Django itself? 
It's a bit concerning to me that the project seems like a one man show as 
there are only 3 other contributors with 3 commits each to your 454 
commits. Do you have a long term interesting in maintaining the module as 
part of Django itself?

Who else would step up to provide expertise here, especially if you have to 
step away for whatever reason?

On Thursday, March 3, 2016 at 6:09:00 PM UTC-5, 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 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/57f5059e-b49d-4d94-9938-2a7dc77540ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to