MySQL Bugs: #52700: forward engineer vs Syncronise

Bug #52700	forward engineer vs Syncronise
Submitted:	8 Apr 2010 17:26	Modified:	12 Dec 2012 14:21
Reporter:	Petronel Laviniu Malutan	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.17	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	error forward engineer

Description:
CREATE  TABLE IF NOT EXISTS `shop`.`u_cn` (

  `ID` INT(10) NOT NULL ,

  `IP` VARCHAR(15) CHARACTER SET 'latin1' COLLATE 'latin1_general_ci' NOT NULL DEFAULT '' ,

  `DATE` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00' ,

  `WEBPAGE` LONGTEXT CHARACTER SET 'utf8' COLLATE 'utf8_unicode_ci' NOT NULL ,

  PRIMARY KEY (`ID`) )

ENGINE = MyISAM

DEFAULT CHARACTER SET = utf8

COLLATE = utf8_unicode_ci

How to repeat:
I don't know how but forward engineer refuses to run the sql's but if syncronise works fine

Could you try with latest version and if problem still persists maybe provide a sample document that helps us reproduce the problem?. thanks in advance

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I reproduce it with Workbench 5.2.44CE and MySQL 5.5.21. 

The last (and only the last) CREATE TABLE sent with forward engineer never specify a DEFAULT CHARACTER SET. 

This can throws various errors like errno-150 : 
Cannot find an index in the referenced table where the
referenced columns appear as the first columns, or column types
in the table and the referenced table do not match for constraint.

pch

Please try version 5.2.44.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".