Bug #52244 Comments editable without limitation but Error Report when Forward Engineering
Submitted: 20 Mar 2010 20:37 Modified: 23 Mar 2010 10:38
Reporter: Frank Dieffenbach Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.1.18 OS:Windows
Assigned to: CPU Architecture:Any

[20 Mar 2010 20:37] Frank Dieffenbach 
Description:

Error Log for Creating Tables whith long Comments:

Executing SQL script in server

ERROR: Error 1628: Comment for table 'landwerte' is too long (max = 61)

CREATE  TABLE IF NOT EXISTS `mydb`.`Landwerte` (

  `ID` INT NOT NULL AUTO_INCREMENT COMMENT 'Primärschlüssel' ,

  `Bezeichnung` VARCHAR(100) NOT NULL COMMENT 'Bezeichnung' ,

  PRIMARY KEY (`ID`) )

ENGINE = MyISAM

COMMENT = 'Statische Tabelle, enthält die Bezeichnungen der im Webinterface zur Verfügung stehenden Länder'

ERROR: Error 1628: Comment for table 'projekttyp' is too long (max = 61)

CREATE  TABLE IF NOT EXISTS `mydb`.`Projekttyp` (

  `ID` INT NOT NULL AUTO_INCREMENT COMMENT 'Primärschlüssel' ,

  `Bezeichnung` VARCHAR(100) NOT NULL COMMENT 'Bezeichnung' ,

  PRIMARY KEY (`ID`) )

ENGINE = MyISAM

COMMENT = 'Statische Tabelle, enthält die Bezeichnungen der zur Auswahl stehenden Projekttypen.\n'

ERROR: Error 1628: Comment for table 'projektart' is too long (max = 61)

How to repeat:
?
[22 Mar 2010 21:08] Johannes Taxacher 
SE version features a verifcation module that informs the user about problems of that kind. we're planning to improve comment handling for both OSS and SE versions in a later version of workbench.
[23 Mar 2010 10:38] Johannes Taxacher 
this is actually a duplicate of Bug #38597