Bug #107423 MySQL Workbench Crash following AUTO_INCREMENT Keyword
Submitted: 28 May 21:45 Modified: 30 May 10:21
Reporter: Rayshaun Thompson Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.28 OS:Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:x86
Tags: WBBugReporter

[28 May 21:45] Rayshaun Thompson
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\tiddl\AppData\Roaming\MySQL\Workbench\log\wb.log]

When trying to assign AUTO_INCREMENT as an INDEX within table creation, like one would when assigning a UNIQUE INDEX. Attempting to edit the INDEX keyword resulted in immediate crash. In this particular table, there was already a primary key set to AUTO_INCREMENT.

When restarting MySQL workbench, I was able to reconnect to the database which was "Auto-Saved" and all was as I left it. I attempted to highlight the INDEX keyword again to delete it and the crash repeated itself.

This time upon reconnection to the once again "Auto-Saved" database, all of my script tabs were nameless and blank. I was able to reopen the scripts in separate tabs, but the line with the AUTO_INCREMENT INDEX `index_name` (`col_name`) was gone.

No logs were created as a result of this crash.

How to repeat:
I have only replicated this in the singular table with an auto incrementing primary key. Within table creation try to assign AUTO_INCREMENT as an index to the same column already defined as a primary key and auto incrementing. Upon highlighting the keyword INDEX, MySQL Workbench will briefly hang and then crash to desktop.
[28 May 21:47] Rayshaun Thompson
The table this bug is replicated with is the `items` table near the top of the script

Attachment: p0.ddl.sql (application/octet-stream, text), 2.26 KiB.

[28 May 21:48] Rayshaun Thompson
It appears that back-spacing over the keyword rather than highlighting it prevents the crash.
[30 May 10:21] MySQL Verification Team
Hello,

Thank you for the bug report.
I tried to reproduce your issue on windows 10 with MySQL 8.0.29 using the sql file you have provided but I am not seeing any issues at my end.
Please try MySQL Workbench 8.0.29.

Regards,
Ashwini Patil