mysqldump produces incorrect dumps with self-referenced foreign keys
Bug #1732625 reported by
Paulus
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.5 |
Triaged
|
High
|
Unassigned | |||
| 5.6 |
Triaged
|
High
|
Unassigned | |||
| 5.7 |
Triaged
|
High
|
Unassigned | |||
Bug Description
The percona build introduces --innodb-
mysql -e 'create table test (a int, b int, index(a), index(b), foreign key (a) references test(b));' test
mysqldump test test > test.sql
mysql test < test.sql
The expected behaviour is to restore the table and not stop on the create table statement.
Revision history for this message
| Sveta Smirnova (svetasmirnova) wrote | #1 |
| Changed in percona-server: | |
| status: | New → Confirmed |
| tags: | added: regression |
| tags: | added: mysqldump-opt-keys |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Thank you for the report.
Verified as described.