#33169: Migrations crashes with long identifiers on MySQL.
-------------------------------+--------------------------------------
Reporter: Awais Qureshi | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: django32 | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Awais Qureshi):
My information was wrong. On `githubactions` by default mysql is `8.0.26`
but on production we have `mysql5.7`. That was the root cause of the
failure.
Field is available and every thing is fine but `mysql8` triggers this
error and it started appearing in `django30` and upper versions.
Thanks for debugging it helps me a-lot to find out the actual root cause.
Downgrading `mysql` to `5.7` fixed the problem.
Updating the ticket description also.
--
Ticket URL: <https://code.djangoproject.com/ticket/33169#comment:6>
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/066.270ca665d8407e05474dd3dd6966cc83%40djangoproject.com.
