It looks like some code is promoting MySQL's warnings to exceptions. django.db.backends.mysql had that behavior before Django 1.8: https://code.djangoproject.com/changeset/5bcd292098b4de7bb03ef778e24d9e2f433d0dae/
For anyone reporting this, are you using django.db.backends.mysql or some other database engine? If the latter, that backend may be at fault. On Wednesday, August 15, 2018 at 8:12:41 PM UTC-4, Ciaran O'Sullivan wrote: > > I raised this with Django: > https://code.djangoproject.com/ticket/29678 > > It is a MySQL 8 feature that inspectdb seems unable to tolerate.The > information_schema is still utf8 not utf8mb3 or utf8mb4 > Using MySQL 8 for a college project, have My Schema nailed and was going > to use Django to display information. Frustrated is the word. > -- 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+unsubscr...@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/1d6a49b0-dbcb-4890-95ab-c21983d181e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
