Bug #34507 | Table comments are allowed to be too long | ||
---|---|---|---|
Submitted: | 13 Feb 2008 0:14 | Modified: | 11 May 2008 0:21 |
Reporter: | Joe DiFonzo | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.0.13 | OS: | Any |
Assigned to: | Maksym Yehorov | CPU Architecture: | Any |
Tags: | DDL |
[13 Feb 2008 0:14]
Joe DiFonzo
[13 Feb 2008 5:52]
Valeriy Kravchuk
Thank you for a bug report.
[22 Feb 2008 11:54]
Maksym Yehorov
Added fix to validate this by using menu option Module/Validation (MySQL)/Validate All. Needs to be rescheduled for later add-on of real-time check.
[8 Apr 2008 12:43]
Mike Lischke
validation is in place so we can close that.
[8 Apr 2008 20:39]
Johannes Taxacher
validation of too long comments works. (tested in SVN Rev 3011)
[11 May 2008 0:21]
Paul DuBois
Noted in 5.0.18 changelog. Workbench allowed table comments to be entered longer than the maximum length of 60 characters.
[29 Apr 2009 14:59]
MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=44543 marked as duplicate of this one.
[9 Jun 2010 10:44]
Marc Giles
What would work better for me is that comments 60 characters or more are allowed in the modeller but provide an option to not forward engineer the comments (so they exist in the model but not the DB). Either that or to have a separate db comment field and a longer comment field purely for the data model.
[27 Feb 2011 14:45]
Ruben A
Does not work for me in 5.2.31. Regression?
[21 Mar 2011 12:06]
Kevin Swift
I really useful fix for this would be to add an option in the export command to not export all the comments. After all one of the main purposes of workbench is to document your schema and restricting comment size in workbench would be a very bad solution to this problem. Adding an option of not exporting comments or simply truncating them would be very useful indeed.