Bug #54985 Discrepancy between Validation (MySQL) in Workbench SE and script execution
Submitted: 3 Jul 2010 17:13 Modified: 2 Sep 2010 14:20
Reporter: Christopher Gribble Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.25 SE Revision 6303 OS:Windows (Version 7)
Assigned to: Maksym Yehorov CPU Architecture:Any

[3 Jul 2010 17:13] Christopher Gribble
Description:
For a particular schema under development, selecting Validate (SQL) from the Model menu then selecting the Validate All option reports no errors.  Selecting Forward Engineer from the Database menu and selecting Run Validations also reports no errors.  However, executing the SQL script causes "ERROR: Error 1005: Can't create table 'xxx' (errno: 150)" to be logged.  One would expect consistency in the analysis.

How to repeat:
See Description.

Suggested fix:
Make validation checks consistent within MySQL and all associated tools.
[3 Jul 2010 19:34] Valeriy Kravchuk
Please, upload .mwb file to demonstrate the problem.
[5 Jul 2010 13:27] MySQL Verification Team
Verified on Fedora 13 X86_64:

Executing SQL script in server
ERROR: Error 1005: Can't create table 'My_Schema.Table_2' (errno: 150)
[24 Aug 2010 19:28] Maksym Yehorov
Fix committed.
[25 Aug 2010 16:07] Johannes Taxacher
fix confirmed in repository
[2 Sep 2010 14:20] Tony Bedford
An entry has been added to the 5.2.27 changelog:

Selecting Validate (SQL) from the Model menu and then selecting the Validate All option reported no errors. Selecting Forward Engineer from the Database menu and selecting Run Validations also reported no errors. However, executing the SQL script caused the following error:

ERROR: Error 1005: Can't create table 'xxx' (errno:150)