MySQL Bugs: #38621: Add separate note field to table properties as the comment is too small

Bug #38621	Add separate note field to table properties as the comment is too small
Submitted:	7 Aug 2008 7:22	Modified:	7 Aug 2009 13:55
Reporter:	Mike Lischke	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.0.24	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	CHECKED, comments, table editor

Description:
From a customer: The comment on a table is very small (60 chars), it’s it 
possible to have a notation field that can be exported to the HTML DB 
docs, where we can put at lot more text?

How to repeat:
See limited comment field in table editor.

Suggested fix:
Add new notes field.

Thank you for a reasonable feature request.

Bug #41277 was marked as a duplicate of this one.

Bug #41985 is a duplicate of this bug here.

Bug #44439 is set as duplicate of this bug here

We won't add a new notes/comments field as this is getting confusing, so this feature request will be closed. 

However, we are going to add a special feature in the comment field that behaves like this:

1) Everything in the first line (up, but not including the line break) or the first 60 characters (the limit in such comments in a MySQL object), whichever is shorter, is synch'ed with the db.
2) The rest is always kept as it is and never compared to any text in a DB.
3) There will be (switchable) visual markers that show what goes into the DB and what stays only in the model.

So if you want to have no DB comment but a note in the model add a line break first. The only drawback is that you cannot have a line break in your comment that goes into the DB, but that's only a small limitation.

Bug #38597 keeps track of the new implementation.