Merge lp://staging/~akopytov/percona-server/RDBA-bug1081016-5.1 into lp://staging/percona-server/5.1
| Status: | Merged |
|---|---|
| Approved by: | Alexey Kopytov |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 549 |
| Proposed branch: | lp://staging/~akopytov/percona-server/RDBA-bug1081016-5.1 |
| Merge into: | lp://staging/percona-server/5.1 |
| Diff against target: |
302 lines (+196/-22) 4 files modified
Percona-Server/client/mysqldump.c (+121/-21) Percona-Server/configure.in (+1/-1) Percona-Server/mysql-test/r/percona_mysqldump_innodb_optimize_keys.result (+47/-0) Percona-Server/mysql-test/t/percona_mysqldump_innodb_optimize_keys.test (+27/-0) |
| To merge this branch: | bzr merge lp://staging/~akopytov/percona-server/RDBA-bug1081016-5.1 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Alexey Kopytov (community) | Needs Fixing | ||
| Stewart Smith (community) | Approve | ||
|
Review via email:
|
|||
Description of the change
Bug #1081016: mysqldump --innodb-
The problem was that mysqldump --innodb-
SQL for cases when there was an explicitly named FK constrained which
implied a implicit secondary index with the same name. An attempt to
skip such a key definition from table schema and add it later with an
ALTER TABLE statement resulted in an "Incorrect index name" error,
because an index with the same name has already been created implicitly.
Fixed by detecting such cases in skip_secondary_
the secondary to table schema in case there's an explicitly named FK
constraint with the same name.
http://
| Stewart Smith (stewart) | # |
| Alexey Kopytov (akopytov) wrote | # |
Wrong merge from the (originally prerequisite) branch for bug #989253. It should not remove the "ALTER TABLE `t1` ADD KEY `c` (`c`);" line from the .result file.