Bug #61393 Incorrect SQL syntax in Forward Engineer
| Submitted: | 3 Jun 2011 8:02 | Modified: | 29 Nov 2011 14:23 |
|---|---|---|---|
| Reporter: | mam tud | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
| Version: | 5.2.34 , Revision 7780 | OS: | Windows (XP) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | erorr;SQL;syntax;export;forward engineer;phpmyadmin | ||
[3 Jun 2011 8:02]
mam tud
[3 Jun 2011 8:12]
mam tud
wrong category
[3 Jun 2011 8:48]
Valeriy Kravchuk
I've got the following: CREATE TABLE `test`.`new_table` ( `idnew_table` INT NOT NULL , `c1` VARCHAR(45) NULL , PRIMARY KEY (`idnew_table`) ), COMMENT = 'comment' ; on Windows XP when connected to local 5.1.56 server version. Works OK in Modeling part.
[3 Jun 2011 9:16]
mam tud
it should be this: CREATE TABLE `test`.`new_table` ( `idnew_table` INT NOT NULL , `c1` VARCHAR(45) NULL , PRIMARY KEY (`idnew_table`) ) COMMENT = 'comment' ;
[10 Jun 2011 12:34]
Alfredo Kojima
bug #61476 is a duplicate
[29 Nov 2011 14:23]
Philip Olson
Fixed as of 5.2.36: + Exporting SQL for tables that included comments would generate + invalid SQL statements. A comma was missing immediately before + the <literal>COMMENT</literal>.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.