MySQL Bugs: #63408: Generated SQL inserts in wrong order (failing PK requirements)

Bug #63408	Generated SQL inserts in wrong order (failing PK requirements)
Submitted:	23 Nov 2011 20:48	Modified:	30 May 2012 22:10
Reporter:	Javier Ortiz	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.35	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Tries to insert rows in tables with references to other tables not populated yet.

How to repeat:
1) Generate the sql file via Database>Forward Engineer of the attached model.
2) Execute the script in the database

Model for test

Attachment: Xinco.mwb (application/x-zip-compressed, text), 62.82 KiB.

The issue showed on 5.2.32, saw there was an update and retried on the new version with the same result.

Updated model, previous had an error.

Attachment: Xinco.mwb (application/x-zip-compressed, text), 62.82 KiB.

Verified just as described with your .mwb file (after fixing several syntax errors in file generated by Workbench, like comma (',') before COMMENT clause). 

Looks like INSERTs are generated with foreign keys in place just in the alphabetical order of table names, without any regard to foreign key contraints present.

The model attached contains duplicated table name xinco_core_user (looks like one of them missing _t) with 1st table holding inserts and 2nd constraints. Thus leading to table with constraints being created in correct order, but inserts are generated in regards to 2nd table that doesn't have any constraints and thus haven't any INSERTS ordering.

The tables are not duplicate. They are different and on purpose. The one with the _T is an audit trail table that basically holds all the data in the original one and some additional data in related tables. I still believe is a bug.

I see 2 tables called xinco_core_user in your model.

Clarifying, you have 2 tables called xinco_core_user and an extra xinco_core_user_t.
Check int the Overview table list or the Catalog tree.