#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: invalid
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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Thanks for extra details and a sample project.
I was able to reproduce this error, however Django is not at fault, it
seems to be an issue in MySQL itself. Django executes:
{{{#!sql
CREATE TABLE
`ticket_33169_whiteboxstudentsexaminationdatatransferauditionf7bf` (
`id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
`unique_student_enrollment_id` integer UNSIGNED NOT NULL CHECK
(`unique_student_enrollment_id` >= 0)
)
}}}
(I called my app `ticket_33169`) so
`ticket_33169_whiteboxstudentsexaminationdatatransferauditionf7bf_chk_1`
is a internal name generated by MySQL. Surprisingly, MySQL doesn't respect
its own limitations.
--
Ticket URL: <https://code.djangoproject.com/ticket/33169#comment:14>
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/0107017f59d4ff62-592cdfb3-56d2-4ea3-b4a2-04212a51120f-000000%40eu-central-1.amazonses.com.
