Bug #92859 Error parsing DDL for a specific table
Submitted: 19 Oct 2018 9:31 Modified: 22 Oct 2018 7:07
Reporter: Mauro Molinari Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.12 OS:Any
Assigned to: CPU Architecture:Any

[19 Oct 2018 9:31] Mauro Molinari
Description:
When I right click on one of my tables in the schemas/tables navigator to alter it, I get the following error:

Error parsing DDL for `myschema`.`MY_TABLE`.
There was an error while parsing the DDL retrieved from the server.
Do you want to view the DDL or cancel processing it?

If I hit "View DDL" I get the following the in the SQL editor:

delimiter $$

CREATE TABLE `PEC_MAILBOXES` (
  `serviceInstanceId` int(11) NOT NULL,
  `name` varchar(255) NOT NULL,
  PRIMARY KEY (`serviceInstanceId`),
  KEY `Name_idx` (`name`),
  CONSTRAINT `PecMailboxServiceInstance_FK` FOREIGN KEY (`serviceInstanceId`) REFERENCES `SERVICE_INSTANCES` (`id`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Summary table that lists all PEC mailboxes handled by us. It''s a somewhat redundant view of the relationship between a service instance and the mailbox bought with the PEC order product of the first service activation of that service instance, populated when the mailbox is activated the first time, or whenever a new service instance for it is created due to a mailbox owner change. It''s maintained to allow for easy querying for simple PEC statistics without the need to retrieve the mailbox name from the order product custom parameters (which requires deep joins and a careful selection), but of course it''s important that it''s maintained updated in a consistent way over time.'$$

Also, the SQL editor shows some syntax errors on the doubled single quotes within the COMMENT clause and I'm not sure why.

How to repeat:
Create a table with the DDL above (probably irrelevant, but if you need the referenced SERVICE_INSTANCES table just add one with an INT(11) primary key named id). Then try to Right click on it from the schemas navigator and choose "Alter Table...".
[19 Oct 2018 11:58] MySQL Verification Team
Thank you for the bug report.
[22 Oct 2018 7:07] Mike Lischke
Duplicate of Bug #92191.