#33169: Migrations crashes with long identifiers on MySQL (8.0.26 )
-------------------------------------+-------------------------------------
Reporter: Awais Qureshi | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
django32,mysql8.0.26 | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Awais Qureshi):
I have created a simple app to reproduce this issue. You can see three
`github` checks are running and `django30` and `django32` are showing
error. Since this feature was introduced in `django30`.
This change is related with Added support for check constraints on MySQL
8.0.16+. [https://github.com/django/django/pull/11743]
Sample project with long table name where `mysql8` and `django` is
generating internal checks if model has PositiveIntegerField.
Possible solution:
In case of `makemigrations` trigger some error with max length or truncate
the check name.
In case of upgrading existing project from `mysql57` to `mysql80` show
some valid error message during `migrate` command.
--
Ticket URL: <https://code.djangoproject.com/ticket/33169#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017f59d0d0a8-8f853f54-a674-4800-9c68-70f3fe0e915d-000000%40eu-central-1.amazonses.com.
