[MDEV-16334] Incorrect ALTER TABLE for changing column option Created: 2018-05-30 Updated: 2018-05-30 Resolved: 2018-05-30 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Mroonga |
| Affects Version/s: | 10.3.6 |
| Fix Version/s: | 10.3.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | regression | ||
| Issue Links: |
|
||||||||
| Description |
|
A code refactoring accidentally changed ALTER_COLUMN_OPTION and ALTER_COLUMN_STORAGE_TYPE to be separate flags. InnoDB and Mroonga are only checking for the latter; the example storage engine is checking for the former only. The impact of this bug should be incorrect operation of Mroonga when the column options GROONGA_TYPE, FLAGS are changed. InnoDB does not define any column options, only table options, so the flag ALTER_COLUMN_OPTION should never be set. |
| Comments |
| Comment by Marko Mäkelä [ 2018-05-30 ] |
|
analysis, fixing and testing |