Re: Questions about MySQL notes in Django docs

Yes, Django supports MySQL 8. If you google "django mysql 8" the second result is https://code.djangoproject.com/ticket/29451. Based on the commits there, it looks like Django 2.0.7 and above received the fixes.

On Wednesday, January 23, 2019 at 5:10:18 AM UTC-5, Carsten Fuchs wrote:

Dear Django group,

can you please help me with some questions about
https://docs.djangoproject.com/en/2.1/ref/databases/#mysql-notes ?
(I've been using Django with an Oracle database for years, but I'm new
to MySQL.)

a) Does "Django supports MySQL 5.6 and higher." cover MySQL 8? (I'm not
sure about the status of some tickets and PRs.)

b) Why is the "mysqlclient" client the recommended choice?

c) Using MySQL 8 and considering
https://code.djangoproject.com/ticket/18392, should we set utf8 or
utf8mb4 as the character set?
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html
indicates that utf8 is an alias to the deprecated utf8mb3 even with MySQL 8.

d) Why is isolation level "read committed" preferred over "repeatable
read"? The text says "Data loss is possible with repeatable read.", but
how can "repeatable read" have data loss that "read committed" has not?

Thank you!

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/8881bcd7-2d9e-4e2d-abf8-8dd840dfdbaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.