Bug #17965 | Comments are not comitted to the DB. | ||
---|---|---|---|
Submitted: | 6 Mar 2006 14:15 | Modified: | 10 May 2006 13:37 |
Reporter: | Stefaan Lesage (Basic Quality Contributor) | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Workbench Preview | Severity: | S3 (Non-critical) |
Version: | 1.0.6 Beta | OS: | Windows (Windows XP) |
Assigned to: | CPU Architecture: | Any |
[6 Mar 2006 14:15]
Stefaan Lesage
[6 Mar 2006 15:58]
MySQL Verification Team
Verified on Windows 2000 SP4, latest patches. The synchronization process generated SQL like this: CREATE TABLE `table_02` ( `idtable_02` int(11) unsigned NOT NULL auto_increment, PRIMARY KEY (`idtable_02`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 But it should have generated this: CREATE TABLE `table_02` ( `idtable_02` int(11) unsigned NOT NULL auto_increment COMMENT 'fieldcomment', PRIMARY KEY (`idtable_02`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1
[10 May 2006 13:37]
Stefaan Lesage
Update for 1.0.6 Beta. Table comments apparently do not seem to get saved in the model. Field comments do. Though when synchronising your model with the DB, or exporting a Create Script for your model, the comments are not applied to the DB.