Re: Questions about MySQL notes in Django docs

Hi Jason,

Am 24.01.19 um 14:47 schrieb Jason:
> It doesn't look like the fixes were backported to 1.11, after looking in the django 1.11 release notes.
> As Tim said, 
>> Based on the commits there, it looks like Django 2.0.7 and above received the fixes

Yes, that's part of my problem.

My project is already at Python 3.6 and normally I would now work through Django versions 2.0, 2.1 and soon 2.2, upgrading and testing at each iteration.

Unfortunately, Django 2.0 does no longer support Oracle 11 while Django 1.11 doesn't have the MySQL fixes referenced by Tim.

That means that I'd be forced to switch from Django 1.11 to Django 2.0 and from Oracle 11 to MySQL 8 simultaneously – and that is more risk that I can bear. (Being able to follow Django's point releases at a reasonable pace is my main personal motivation for switching the database. Being stuck is really frustrating.)

Thus, the first step that I have to take is to switch the database to MySQL 8 at Django 1.11.
Thus my question: ticket #29451 doesn't seem to affect my use case, but is there anything else that I should be aware of when using MySQL 8 at Django 1.11?

For example, web search leads to https://stackoverflow.com/questions/49949480/test-django-with-mysql-8-0-datetime-incompatible
However, I'm not experienced enough with MySQL 8 to draw the proper conclusions: Will Django 1.11 work anyways with the latest connector? https://bugs.mysql.com/bug.php?id=90541 suggests a work-around (for Django 2.0), but does the datetime problem affect the recommended "mysqlclient" connector as well?

Which brings me back to my other questions:

b) Why is the "mysqlclient" client the recommended choice? --- quite the opposite is suggested at https://dev.mysql.com/doc/connector-python/en/

c) Regarding utf8, utf8mb3 and utf8mb4 there is conflicting information as well (https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html), but I can figure that out on my own.

Best regards,
Carsten

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9fc409a5-814d-25df-9b74-a7418d75baea%40cafu.de.
For more options, visit https://groups.google.com/d/optout.