Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.8
-
None
-
Docker version 17.06.0-ce, build 02c1d87 running on OSX 10.12.4 (16E195)
Docker image SHA: 801ba73f78da191339d1cf2acdb98f2ea6fe2d38974e838a4a5f1535563e4ed7
Description
In the 10.2.8 update the following script will fail. When testing against 10.2.7 it will not fail indicating a regression between bugfix versions.
Test Case
create table X (
|
A int,
|
b int,
|
primary key (A,B)
|
);
|
 |
ALTER TABLE X DROP COLUMN A;
|
Expected Result
The column is dropped from the table
Actual Result
An error is returned
[42000][1072] Key column 'A' doesn't exist in table
|
In 10.2.7 docker, as specified by the sha 8ea33570152349b827d7121b88dc3f44a64e1cc7646cfae01faee4824b9b0007 the above script will work and drop the column.
Attachments
Issue Links
- is duplicated by
-
MDEV-14738 Replication breaks when dropping a column of a combined primary key (with a confusing error message)
- Confirmed
- relates to
-
MDEV-11114 Cannot drop column referenced by CHECK constraint
- Closed
-
MDEV-13625 Merge InnoDB test cases from MySQL 5.6
- Closed
-
MDEV-13626 Merge InnoDB test cases from MySQL 5.7
- Closed
-
MDEV-21097 Incorrect error message when trying to delete column which is part of unique key constraint
- Closed
-
MDEV-24690 Dropping primary key column from versioned table always fails with 1072
- Closed