Bug #99401 Synchronize Model Error at change table name.
Submitted: 29 Apr 2020 16:03 Modified: 25 Jul 2020 10:22
Reporter: Sergio Orestes Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:8.0.19 OS:Debian (Debian 10 x86_64)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[29 Apr 2020 16:03] Sergio Orestes 
Description:
No relevant informations

How to repeat:
ALTER TABLE `shelfqa`.`spxtbluserprofile` 
DROP COLUMN `corName`,
DROP COLUMN `corUpdDate`,
DROP COLUMN `corInsDate`,
DROP COLUMN `corId`,
ADD COLUMN `corId` INT(11) NOT NULL FIRST,
ADD COLUMN `corInsDate` DATETIME NOT NULL AFTER `corId`,
ADD COLUMN `corUpdDate` DATETIME NOT NULL AFTER `corInsDate`,
ADD COLUMN `corName` VARCHAR(45) NOT NULL AFTER `comId`,
DROP PRIMARY KEY,
ADD PRIMARY KEY (`corId`),
ADD INDEX `ix_cor_comId` (`comId` ASC),
ADD INDEX `ix_cor_rstId` (`rstId` ASC),
DROP INDEX `ix_cor_rstId` ,
DROP INDEX `ix_cor_comId` ; <-- ERROR
, RENAME TO  `shelfqa`.`spxtblcompanyrole` ;

Suggested fix:
ALTER TABLE `shelfqa`.`spxtbluserprofile` 
DROP COLUMN `corName`,
DROP COLUMN `corUpdDate`,
DROP COLUMN `corInsDate`,
DROP COLUMN `corId`,
ADD COLUMN `corId` INT(11) NOT NULL FIRST,
ADD COLUMN `corInsDate` DATETIME NOT NULL AFTER `corId`,
ADD COLUMN `corUpdDate` DATETIME NOT NULL AFTER `corInsDate`,
ADD COLUMN `corName` VARCHAR(45) NOT NULL AFTER `comId`,
DROP PRIMARY KEY,
ADD PRIMARY KEY (`corId`),
ADD INDEX `ix_cor_comId` (`comId` ASC),
ADD INDEX `ix_cor_rstId` (`rstId` ASC),
DROP INDEX `ix_cor_rstId` ,
DROP INDEX `ix_cor_comId` --> REMOVE ";"
, RENAME TO  `shelfqa`.`spxtblcompanyrole` ;
[25 Jun 2020 10:22] MySQL Verification Team 
Hello Sergio Orestes,

Thank you for the report.
Could you please provide exact Workbench model(.mwb) to reproduce this issue at our end? Thank you.

regards,
Umesh
[26 Jul 2020 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".