Re: 3719: 'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 - When using MySQL sakila and world DB examples
I added a comment with a workaround to the Django Ticket. https://code.djangoproject.com/ticket/29678 Included is the settings.py and the changes made. -- 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/01545110-b3eb-4198-aa42-2614999dc04e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: 3719: 'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 - When using MySQL sakila and world DB examples
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.
Re: 3719: 'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 - When using MySQL sakila and world DB examples
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/f9e93d1d-6d1c-481c-b08f-60a7e7348ec3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: 3719: 'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 - When using MySQL sakila and world DB examples
Downgrading to 5.7.7 and installing "mysql-connector-python 8.0.11" through pip fixed the issue. Is this because the mysql-connector-python from MySQL/Oracle does not work with their own MySQL 8.0.11 version? thanks -Ram On Friday, July 13, 2018 at 9:18:39 AM UTC+5:30, Ram Munjuluri wrote: > > thanks Melvyn. let me try to downgrade to MySQL 5.7.7 first. > > > > On Friday, July 13, 2018 at 3:13:23 AM UTC+5:30, Melvyn Sopacua wrote: >> >> On donderdag 12 juli 2018 19:27:23 CEST Ram Munjuluri wrote: >> >> > from django.db import models >> > # Unable to inspect table 'city' >> > *# The error was: (3719, "3719: 'utf8' is currently an alias for the >> > character set UTF8MB3, which will be replaced by UTF8MB4 in a future >> > release. Please consider using UTF8MB4 in order to be unambiguous.", >> None)* >> > >> > Any suggestion here please? I seem to be stuck here. >> >> Downgrade to MySQL 5.x or patch PyMySQL. More info: >> https://github.com/PyMySQL/PyMySQL/issues/690 >> >> -- >> Melvyn Sopacua >> > -- 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/9fa45c4b-1eec-4d08-ab95-004d91647bca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: 3719: 'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 - When using MySQL sakila and world DB examples
thanks Melvyn. let me try to downgrade to MySQL 5.7.7 first. On Friday, July 13, 2018 at 3:13:23 AM UTC+5:30, Melvyn Sopacua wrote: > > On donderdag 12 juli 2018 19:27:23 CEST Ram Munjuluri wrote: > > > from django.db import models > > # Unable to inspect table 'city' > > *# The error was: (3719, "3719: 'utf8' is currently an alias for the > > character set UTF8MB3, which will be replaced by UTF8MB4 in a future > > release. Please consider using UTF8MB4 in order to be unambiguous.", > None)* > > > > Any suggestion here please? I seem to be stuck here. > > Downgrade to MySQL 5.x or patch PyMySQL. More info: > https://github.com/PyMySQL/PyMySQL/issues/690 > > -- > Melvyn Sopacua > -- 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/9781ea56-868f-4084-b063-50ba9b35e0fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: 3719: 'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 - When using MySQL sakila and world DB examples
On donderdag 12 juli 2018 19:27:23 CEST Ram Munjuluri wrote: > from django.db import models > # Unable to inspect table 'city' > *# The error was: (3719, "3719: 'utf8' is currently an alias for the > character set UTF8MB3, which will be replaced by UTF8MB4 in a future > release. Please consider using UTF8MB4 in order to be unambiguous.", None)* > > Any suggestion here please? I seem to be stuck here. Downgrade to MySQL 5.x or patch PyMySQL. More info: https://github.com/PyMySQL/PyMySQL/issues/690 -- Melvyn Sopacua -- 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/2218292.uKYFzWeVbL%40fritzbook. For more options, visit https://groups.google.com/d/optout.
