MySQL Bugs: #47380: Too long comment for table '<TABLE

Bug #47380	Too long comment for table '<TABLE_NAME>'
Submitted:	16 Sep 2009 15:43	Modified:	10 Nov 2009 14:13
Reporter:	arnaud lemercier	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.18	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any
Tags:	comment, error 1105, table

Description:
When I write a long comment on a table with MySQL Workbench, the forward Engineering failed.

########## LOGS ############
Executing SQL script in server
ERROR: Error 1105: Too long comment for table 'example'

-- -----------------------------------------------------
-- Table `mydb`.`Example`
-- -----------------------------------------------------
CREATE  TABLE IF NOT EXISTS `mydb`.`Example` (
  `idExample` INT NOT NULL ,
  PRIMARY KEY (`idExample`) )
ENGINE = InnoDB
COMMENT = 'This is a long comment with more than 60 caracters. This is not bloc in the IDE but script failed.'

####### END OF LOGS ########

How to repeat:
 1 - Create a new table "Example"
 2 - Add a long comment
 3 - Start forward Engineering (Ctrl+G)

Suggested fix:
Block textfield to 60 caracters

Example MySQL Workbench File

Attachment: BUG_47380.mwb (, text), 3.80 KiB.

Looks like a duplicate of http://bugs.mysql.com/bug.php?id=43517. Check Susanne's comments there.

Sorry, I'm French and I'm not sure I understand correctly.

The description fields are preserved for documentation of the SE version? 
Is there any adjustment provided for the OSS version?
Can you keep this unlimited field and correct that the forward engineering exports only the first 60 characters?

This:

"Can you keep this unlimited field and correct that the forward engineering exports only
the first 60 characters?"

sounds like a nice and useful feature request, for OSS edition at least. Thank you.

There's no special handling of too long comments in tables. Only SE version has a validation module that alerts the user of having oversized comments in a table object.

This is a feature we have on the list for 5.2 where we'll let WB sync the first 60 chars (or first line) of a comment to/from database (also including visualization of this behaviour in the editor)

This is a duplicate of bug #38597