MySQL Bugs: #39121: Export successful, but then "ERROR 1105 (HY000): Too long comment for table"

Bug #39121	Export successful, but then "ERROR 1105 (HY000): Too long comment for table"
Submitted:	29 Aug 2008 14:35	Modified:	2 Sep 2008 11:58
Reporter:	Andrew Krizhanovsky	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.24	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
It's possible to write too long comments in MySQL Worbench.

If you export such script then the tables with these long comments will not be created by MySQL. The error will be produced:

ERROR 1105 (HY000): Too long comment for table

How to repeat:
Enter the following table description:

Meaning includes:
1) a definition (preceded by "#"), or translation for foreign words;
2) semantic relations
3) translations

Suggested fix:
Do not constraint the user possibility to write long comments, but give him a warning or hint.

Thank you for a problem report. Had you tried to validate your schema before exporting with Module/Validation (MySQL)/Validate All menu option? Validation should inform you about the potential problem (see Bug #34507).

Menu item "Validation (MySQL)" is disabled in "The Community Edition (OSS)".

OK, then Workbench OSS should at least give a warning when exporting SQL CREATE script. This is a verified bug.

Actually, this is considered not to be a bug. The possibility to enter longer description than the mysql-server allows, has been left open for documentation purposes (so you can store longer description in your model file in case you don't want to put your model directly to a DB server).
SE version has a validation-plugin to warn users about too long comments.
When using the OSS Edition we assume that people have a high skill level and know what they are doing. For everybody else the Standard Edition provides the convenience of checking for possible problems like these on command.

Bug #41414 is a duplicate of this bug here.

This is not a very satisfactory solution to this issue.  A better approach would be to provide an option that allows one to either 
a) not export comments at all
or
b) truncate comments to fit within the allowed field size

For those of us who like to keep detailed comments in our models, it's frustrating (and time consuming) to have to go through and strip out the comments in the generated script before it can be applied.

I fully agree with Craig Nicholls.

I'm using 5.2.14OSSb Rev4990.

Since August-2008 until now, the inconvenience persists.

I wrote detailed information about my table, and I don't want to export the comments.

Is it possible to include a check-box with "Don't export comments" ?

It would be wonderful and useful. Then, we would be able to store in workbench all definitions and details (the main purpose), and send to mysql-database only the necessary objects to work.

I agree with Allan,,

actually this feature was available in DB designer, when you can choose to create DDL code without comments, it will be very nice to add this feature to MySQL Workbench