Bug #76514 Table and index comments destroy the exported SQL code.
Submitted: 28 Mar 2015 0:58 Modified: 17 Nov 2015 15:45
Reporter: Fotis Kokkoras Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:6.3.5 OS:Microsoft Windows (Microsoft Windows 7 Professional)
Assigned to: CPU Architecture:Any
Tags: comment truncated, table comments

[28 Mar 2015 0:58] Fotis Kokkoras
Description:
Having a long table comment in a database model, produces a COMMENT line in the exported SQL script that is broken (comment truncated). 

How to repeat:
create a model, add a table, and add this text for table comments:

Thesis assignments to student-users - many-to-many because a student can have all of his theses in to the system (bsc, msc, phd, ktl). Moreover, a thesis can be assigned to more than one student users.

Exporting the model results in the following COMMENT line:

COMMENT = 'Thesis assignments to student-users - many-to-many because a' /* comment truncated */ /* student can have all of his theses in to the system (bsc, msc, phd, ktl). Moreover, a thesis can be assigned to more than one student users.*/;
[30 Mar 2015 22:48] MySQL Verification Team
Please provide a model project test file. Thanks.
[30 Mar 2015 23:37] Fotis Kokkoras
model to repeat issues #74530 and #76514

Attachment: x.mwb (application/x-zip-compressed, text), 6.33 KiB.

[30 Mar 2015 23:38] Fotis Kokkoras
exported SQL with truncated comments

Attachment: x.sql (application/octet-stream, text), 1.60 KiB.

[31 Mar 2015 7:02] MySQL Verification Team
Thank you for providing the requested model file.
I'm able to confirm this with 6.3.2 and 6.2.5 on Win7.

Thanks,
Umesh
[17 Nov 2015 15:45] Fotis Kokkoras
Long table comments and index comments are not exported well in the Forw. Eng. SQL Script task. They actually destroy the SQL code that is exported. 

Long comments on columns seem to work well (they are exported OK).

The bug ahs been reported again in versions 6.2.5 and 6.3.2