I think that given Adams plan it might be possible to get this done before 2.2 as there are not too many failures. I’m not entirely convinced that including MariaDB logic inside the MySQL backend is a permanent solution.
It might be the path of least resistance right now, and a good idea to get this in before 2.2, but if we care enough to make a fully supported backend then we might also care enough to remove any workarounds we have for MySQL (like 27676 <https://code.djangoproject.com/ticket/27676> + and others we discover), plus support any additional features or syntax that MariaDB includes. This could get pretty complex if we shoehorn it into one backend because we are going to be supporting a larger compatibility matrix. On 5 July 2018 at 14:45:35, Carlton Gibson ([email protected]) wrote: This seems a bit more pressing now: 2.0.7 broke MariaDB compatibility. https://code.djangoproject.com/ticket/29544 I'm sure that can be fixed. But we're in a tricky position now. Claude has marked the ticket as a Release Blocker, which is understandable, but I can't see how we can both support and not-support MariaDB, especially when we don't have test coverage on CI to support it. Adam, you came to mind immediately when I saw the ticket here, since you've talked about this. (So I'm glad you're already on this thread.) Where are we on MariaDB support? What timescale can we add it (if at all)? What can we realistically do in the interim? v2.2 is scheduled for the end of 2018. That's the earliest we can get it in now. What's a realistic workflow if we're going to consider MariaDB breaking changes as out of bounds before then? Thanks for the input all! C. -- 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/4cf1e564-e0ad-4576-ba53-4d9276633cff%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/4cf1e564-e0ad-4576-ba53-4d9276633cff%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 [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/CAFNZOJNb6n9Yp81KixvubewqwVe62erTw-WAvfNMycB3UFAm_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
