Bug #114882 Unexpected incompatibility in InnoDB Foreign Key constraint with Error 6125
| Submitted: | 5 May 2024 8:00 | Modified: | 7 May 2024 4:45 |
|---|---|---|---|
| Reporter: | Tsubasa Tanaka (OCA) | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 8.4.0 | OS: | CentOS (7.9) |
| Assigned to: | CPU Architecture: | x86 | |
| Tags: | ER_FK_NO_UNIQUE_INDEX_PARENT, Failed to add the foreign key constraint, Missing unique key | ||
[5 May 2024 8:00]
Tsubasa Tanaka
[6 May 2024 5:56]
liu rundong
I have the same problem with docker mysql:latest. At first I thought it was caused by docker or something else, and google it can't get result. Finally find problem here. I also test for 8.0 - 8.3 by docker, they don't have this problem.
[6 May 2024 10:20]
Sinhuè Angelo Rossi
It happens also on Windows, I cannot restore a dump created with MySQL 8.0.
[7 May 2024 4:44]
MySQL Verification Team
Hello tanaka-San, Thank you for the report and feedback. If you have no objections then will mark this as a duplicate of Bug #114838( even though Bug #114882 has a test case but since same issue was reported earlier here Bug #114838). Thank you. regards, Umesh
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.051 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.