Bug #88118 Upgrading to 8.0.3 fails if foreign keys of exactly 64 characters are present
| Submitted: | 17 Oct 2017 9:50 | Modified: | 23 Oct 2017 14:42 |
|---|---|---|---|
| Reporter: | Daniël van Eeden | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 8.0.3 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | compatibility, foreign keys, upgrade | ||
[17 Oct 2017 9:50]
Daniël van Eeden
[17 Oct 2017 9:56]
Daniël van Eeden
The django backend for mysql defines the maximum length as 64. https://github.com/django/django/blob/master/django/db/backends/mysql/operations.py#L194
[17 Oct 2017 10:24]
MySQL Verification Team
Hello Daniël, Thank you for the report. Verified as described. Thanks, Umesh
[17 Oct 2017 10:26]
MySQL Verification Team
test results
Attachment: 88118.results (application/octet-stream, text), 6.55 KiB.
[19 Oct 2017 12:38]
Naga Satyanarayana Bodapati
Posted by developer: Not possible to change the limit. Please fix the docs. the query should use ">=" instead of ">".
[23 Oct 2017 14:42]
Daniel Price
Posted by developer: The documentation has been revised to state that there must be no tables that have foreign key constraint names longer than or equal to 64 characters. https://dev.mysql.com/doc/refman/8.0/en/upgrading.html Thank you for the bug report.
[24 Oct 2017 6:38]
Shane Bester
See https://bugs.mysql.com/bug.php?id=88196
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.