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

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Ram Munjuluri
Hello all,

I posted this question with a different subject line and thought  I would re-post here with the error.

I am using

MySQL 8.0
Python 3.6.5
Django 2.0.7

When I run 

> python manage.py inspectdb --database world city

I get the following error message. Has someone come across this error before? I have dropped the schema and recreated it, but to no effect.


# This is an auto-generated Django model module.
# You'll have to do the following manually to clean this up:
#   * Rearrange models' order
#   * Make sure each model has one field with primary_key=True
#   * Make sure each ForeignKey has `on_delete` set to the desired behavior.
#   * Remove `managed = False` lines if you wish to allow Django to create, modify, and delete the table
# Feel free to rename the models, but don't rename db_table values or field names.
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.

Appreciate it.

kind regards
-Ram

--
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 [hidden email].
To post to this group, send email to [hidden email].
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/9a91c8e0-accb-428e-bf2d-835183e780b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

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

Melvyn Sopacua
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 [hidden email].
To post to this group, send email to [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

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

Ram Munjuluri
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:
<a href="https://github.com/PyMySQL/PyMySQL/issues/690" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FPyMySQL%2FPyMySQL%2Fissues%2F690\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNExfbB5paXsaS0gqxfNsukgcUWNjA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FPyMySQL%2FPyMySQL%2Fissues%2F690\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNExfbB5paXsaS0gqxfNsukgcUWNjA&#39;;return true;">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 [hidden email].
To post to this group, send email to [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

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

Ram Munjuluri
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:
<a href="https://github.com/PyMySQL/PyMySQL/issues/690" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FPyMySQL%2FPyMySQL%2Fissues%2F690\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNExfbB5paXsaS0gqxfNsukgcUWNjA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FPyMySQL%2FPyMySQL%2Fissues%2F690\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNExfbB5paXsaS0gqxfNsukgcUWNjA&#39;;return true;">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 [hidden email].
To post to this group, send email to [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

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

Ciaran O'Sullivan
In reply to this post by Ram Munjuluri
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 [hidden email].
To post to this group, send email to [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

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

Tim Graham-2
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:
<a href="https://code.djangoproject.com/ticket/29678" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcode.djangoproject.com%2Fticket%2F29678\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGQeh_z2WSil8zyNG-esR7VsnBQWg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcode.djangoproject.com%2Fticket%2F29678\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGQeh_z2WSil8zyNG-esR7VsnBQWg&#39;;return true;">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 [hidden email].
To post to this group, send email to [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

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

Ciaran O'Sullivan
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 [hidden email].
To post to this group, send email to [hidden email].
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.