Bug #81805 Alter Table loose checked Auto-Increment
Submitted: 10 Jun 2016 13:08 Modified: 10 Jun 2016 14:18
Reporter: Ricardo Cescon Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.6 OS:Windows
Assigned to: CPU Architecture:Any
Tags: Auto-increment, autoincrement

[10 Jun 2016 13:08] Ricardo Cescon
Description:
If you change as sample the Datatype from MEDIUMINT to INT and the column had checked AI before, Workbench remove now the checked AI.

If you not be attentive, you get really bad problems after executing the ALTER TABLE.

How to repeat:
...
[10 Jun 2016 13:31] MySQL Verification Team
Please try version 6.3.6. Thanks.
[10 Jun 2016 13:34] Ricardo Cescon
Oh crazy, it exists a newer version on web.
If I click on the menu "Check for Updates", it told me "Up to Date"

I will try and come back soon.
[10 Jun 2016 13:37] MySQL Verification Team
OK comment when tested. Thanks.
[10 Jun 2016 13:38] Ricardo Cescon
Same for 6.3.6
[10 Jun 2016 13:51] MySQL Verification Team
Please attach screenshot of each step you did because I wasn't able to repeat (use the Files tab for). Thanks.
[10 Jun 2016 13:58] Ricardo Cescon
step1

Attachment: step1.png (image/png, text), 5.58 KiB.

[10 Jun 2016 13:58] Ricardo Cescon
step2

Attachment: step2.png (image/png, text), 13.73 KiB.

[10 Jun 2016 13:58] Ricardo Cescon
step3

Attachment: step3.png (image/png, text), 5.75 KiB.

[10 Jun 2016 13:58] Ricardo Cescon
step4

Attachment: step4.png (image/png, text), 9.15 KiB.

[10 Jun 2016 14:18] MySQL Verification Team
Thank you for the feedback.
[8 Aug 2017 13:18] Michel Gaudry
This annoying problem is still present in MySQL Workbench 6.3.9 (Win 64 bits)
[4 Jul 2022 15:46] Ondrej Letacek
Hi, I am still having the same issue - it is on Linux workbench version 8.0.25.
This is very annoying as when user change the type (eg smallint to int), it is not expected that the autoincrement will be removed.
[14 Sep 18:03] Omer Barnir
Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.