Bug #46787 Forward Engineer for SQL CREATE does not work
Submitted: 18 Aug 2009 13:56 Modified: 28 Aug 2009 9:40
Reporter: Dennis Becker Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.1.17 OS:Windows (Windows XP SP3)
Assigned to: Alexander Musienko CPU Architecture:Any

[18 Aug 2009 13:56] Dennis Becker 
Description:
I have recently installed WB OSS 5.1.17 and created a new model with some tables and foreign keys, nothing special. After that I wanted to try my model on a MySQL Server, so I run the "Export" => "Forward Engineer SQL CREATE" dialog. As result for exporting all tables, I get the following:

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

How to repeat:
I will add the .mwb file that should help to track the bug down.

Suggested fix:
none
[18 Aug 2009 13:56] Dennis Becker 
my small model

Attachment: the-affinity.mwb (application/octet-stream, text), 10.21 KiB.
[27 Aug 2009 13:54] Johannes Taxacher 
fix confirmed. will be included in 5.1.18
[28 Aug 2009 9:40] Tony Bedford 
An entry has been added to the 5.1.18 changelog:

The Forward Engineer SQL Script wizard generated invalid SQL code for a small model with foreign keys:

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;