-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL error on migrate persists #285
Comments
can you elaborate more on the versions of everything you are using? |
The database is MariaDB 10.1.48, but I deploy on an older version, 5.5.60 |
what is the min version of mySQL supported for django 2.2+? |
That would be MySQL 5.6 which is equivalent to MariaDB 10.1. For MariaDB >= 10.2.2, the server setting |
sorry can't accept any contribution for unsuported versions :) |
You misread what I wrote. Django 2.2 supports MySQL 5.6 and so also MariaDB 10.1, on which the problem happens. |
I'm aware of
DJANGO_CELERY_RESULTS_TASK_ID_MAX_LENGTH
.However migration
0004_auto_20190516_0412.py
still fails withdjango.db.utils.OperationalError: (1709, 'Index column size too large. The maximum column size is 767 bytes.')
because it's trying to create thetask_name
column which is 255-characters long and indexed.The text was updated successfully, but these errors were encountered: