Bug #33093 Import from SQL syntax error w/CONSTRAINTS
Submitted: 8 Dec 2007 23:10 Modified: 9 Dec 2007 22:22
Reporter: Nick Gaugler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.10 OSS Beta OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: import sql innodb constraints mysqldump

[8 Dec 2007 23:10] Nick Gaugler 
Description:
Workbench syntax errors while trying to import from SQL on lines that contain CONSTRAINT dumped from mysqldump.

How to repeat:
Create a database a few tables with InnoDB tables and constraints in MySQL 5.0.x.  Use mysqldump to dump the structure to a .sql file.  GO to File -> Import -> Reverse Engineer MySQL Create Script

Suggested fix:
Develop application to support all structures that can be dumped by mysqldump.
[9 Dec 2007 7:27] Valeriy Kravchuk 
Thank you for a problem report. Please, send simple .sql file to demonstrate this problem.
[9 Dec 2007 22:22] Nick Gaugler 
Please close this bug.  This problem only exists if routines are in the .sql file.  Oddly enough, the application does not only skip routines, but it skips actual tables as well.  

When I remove the routines from the dump (by removing -R option from the mysqldump), all tables import correctly.  Probably a duplicate of bug 32885.