#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 Jacob Walls):
Have you verified the model field referred to is still in your project? I
can produce your error if I'm executing a previously written migration but
where the field is no longer in my project. Instead, if the field is in my
project, I get this upon `migrate`:
{{{
SystemCheckError: System check identified some issues:
ERRORS:
x.xxxx: (models.E018) Autogenerated column name too long for field
"blackboard_blackboardlearnerassessmentdatatransmissionaudit_chk_1".
Maximum length is "64" for database "default".
HINT: Set the column name manually using 'db_column'.
}}}
This system check predates 2.2, so if the field is in your project and no
system check is raised, that would be a false negative to address. But we
would need a minimal project to verify that the field exists.
--
Ticket URL: <https://code.djangoproject.com/ticket/33169#comment:4>
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.9d74e60afcd3af8b3edbcb99d7e76a5f%40djangoproject.com.
