Unable to do the initial migrations with django-2.1.3 and "mysql 5.5.62-0+deb8u1 (Debian)"

[Periklis Gkolias]

Hi there,

I am trying to bootstrap a project with mysql and django with the versions
described in the subject line.

The app works fine if I just do a "runserver" and ignore the migration
warning but when I apply the migrations I am getting the stacktrace you can
see in the linked
<https://docs.google.com/document/d/1LijS1KHjn8YbW_B7L_lIYHuqC6pHMRurrq4L9k7i-uc/edit?usp=sharing>
file.


I have seen similar stuff in SO like this
<https://stackoverflow.com/questions/49624954/raise-migrationschemamissingunable-to-create-the-django-migrations-table-s> but
none of the solutions have worked.

I would highly appreciate any piece of documentation to guide me further.
Of course, do not hesitate to contact me if you have any questions.

Thanks,
Periklis

[Simon Charette]

Hello there,

Django 2.1 dropped support for MySQL 5.5[0] as the end of
upstream support is December 2018.

You'll have to update to a more recent version to use Django 2.1+.

Cheers,
Simon

[0]
https://docs.djangoproject.com/en/2.1/releases/2.1/#dropped-support-for-mysql-5-5

Post by Periklis Gkolias
Hi there,
I am trying to bootstrap a project with mysql and django with the versions
described in the subject line.
The app works fine if I just do a "runserver" and ignore the migration
warning but when I apply the migrations I am getting the stacktrace you can
see in the linked
<https://docs.google.com/document/d/1LijS1KHjn8YbW_B7L_lIYHuqC6pHMRurrq4L9k7i-uc/edit?usp=sharing>
file.
I have seen similar stuff in SO like this
<https://stackoverflow.com/questions/49624954/raise-migrationschemamissingunable-to-create-the-django-migrations-table-s> but
none of the solutions have worked.
I would highly appreciate any piece of documentation to guide me further.
Of course, do not hesitate to contact me if you have any questions.
Thanks,
Periklis

[Periklis Gkolias]

Thanks Simon, I havent noticed that.

Post by Simon Charette
Hello there,
Django 2.1 dropped support for MySQL 5.5[0] as the end of
upstream support is December 2018.
You'll have to update to a more recent version to use Django 2.1+.
Cheers,
Simon
[0]
https://docs.djangoproject.com/en/2.1/releases/2.1/#dropped-support-for-mysql-5-5

Post by Periklis Gkolias
Hi there,
I am trying to bootstrap a project with mysql and django with the
versions described in the subject line.
The app works fine if I just do a "runserver" and ignore the migration
warning but when I apply the migrations I am getting the stacktrace you can
see in the linked
<https://docs.google.com/document/d/1LijS1KHjn8YbW_B7L_lIYHuqC6pHMRurrq4L9k7i-uc/edit?usp=sharing>
file.
I have seen similar stuff in SO like this
<https://stackoverflow.com/questions/49624954/raise-migrationschemamissingunable-to-create-the-django-migrations-table-s> but
none of the solutions have worked.
I would highly appreciate any piece of documentation to guide me further.
Of course, do not hesitate to contact me if you have any questions.
Thanks,
Periklis

--
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
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/6fb5c24a-a420-42bf-90bc-fe5e0f35a665%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/6fb5c24a-a420-42bf-90bc-fe5e0f35a665%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.