-
Type:
Bug
-
Status: Done
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: 5.5.59-38.11, 5.6.39-83.1, 5.7.21-20
-
Fix Version/s: 5.7.21-21, 5.5.60-38.12, 5.6.40-84.0
-
Component/s: None
-
Labels:
CREATE TABLE t2 (id int, a int, primary key(id), FOREIGN KEY (a) REFERENCES t2(id)) ENGINE=InnoDB;
implicitly creates
KEY `a` (`a`)
which is taken away to `ALTER TABLE` by optimizer.
Then optimized statement also implicitly creates
KEY `a` (`a`)
what causes that `ALTER TABLE` returns an error.
It is related to https://jira.percona.com/browse/PS-605
- relates to
-
PS-605 LP #1081016: mysqldump --innodb-optimize-keys may produce invalid SQL with explicitly named FK constraints
-
- Done
-
-
PS-1125 LP #1732625: mysqldump produces incorrect dumps with self-referenced foreign keys
-
- Done
-
-
PS-1125 LP #1732625: mysqldump produces incorrect dumps with self-referenced foreign keys
-
- Done
-