Bug #57594 Comment fields for DB schema documentaion too short
Submitted: 20 Oct 2010 8:32 Modified: 26 Oct 2010 22:43
Reporter: Micha Stone Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S4 (Feature request)
Version:5.2.28 OS:Any
Assigned to: CPU Architecture:Any

[20 Oct 2010 8:32] Micha Stone
Description:
MySQL Workbench uses the comment field of the entities to generate a DB schema documentation. The big problem is, that MySQL limits the comments strings to 60 characters. This is enough for short DB comments ut you can never explain a complex table within 60 characters.

Yes, you can insert more than 60 characters but if you execute the creation of the tables you get a MySQL error (comments are too large) or the comments will be cut after 60 characters. There is also no possibility to make a DDL without comments.

How to repeat:
Type in a note for a table or column which is larger than 60 characters. If you execute the DDL script MySQL will produce an error (comments are too large) or the comment will be cut after 60 characters.

Suggested fix:
- Fast workaround: when you export the CREATE SCRIPT there should be the possibility to disable the generation of the comments. So you get valid SQL and can use the comment fields for the docs.

- Desirable fix: Create a new text input area for "notes". These fields are used for larger descriptions an can be used for the documentation. You can place this text input area for tables under the comment text input. For the table columns i suggest to move the comment input as a ne column behind the "Default" inputs of the columns. The note text input area can now be placed at the right side where the comment text input is shown now.
[20 Oct 2010 9:23] Valeriy Kravchuk
Thank you for the feature request.
[26 Oct 2010 22:43] Johannes Taxacher
this is a duplicate of BugĀ #38597