Originally created by: camaro39...@gmail.com
What exact steps will reproduce the problem?
1. Create table `t1` with two columns (`c1`, `c2`) and add PRIMARY index on `c1`
2. Remove `c1` column, press "Save"
What was the expected output?
- "Indexes" tab is updated and empty
What happened instead?
- PRIMARY index is still there. You can't delete it or add PRIMARY index on `c2` without reloading the table
Suggested fix (optional)?
- Care to look into SHOW CREATE TABLE output after each successful ALTER TABLE
- Or analyze, which indexes will be affected after column removal and update "Indexes" tab accordingly (this approach is more difficult and can create more bugz)
Version used?
HeidiSQL revision: 8.0.0.4397
MySQL Server version: MariaDB 5.5.30
Operating system: Windows 7 Ultimate
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
Sounds reasonable.
Labels: Severity-Cosmetic
Status: Accepted
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
This issue was closed by revision [r4419].
Status: Fixed
Related
Commit: [r4419]
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
Done. Refreshing the CREATE TABLE code now after successful "Save" action.