Bug #63934 Forward engineering doesn't generate foreign key for self references

Description:
Opening a model containing a table that has a foreign key to itself isn't generated at all.

This is a complete blocker, please fix ASAP.

How to repeat:
Open/create model with a table that has a one-to-many FK to itself (e.g. from parent_id to id) and forward engineer. The FK declaration is missing.

Thank you for the bug report. Verified with your .mwb file uploaded on Windows XP.

Have you tried setting the storage engine of the tables to InnoDB?

I set every table to "Server Default".

Where do you find the true value then? (Sorry I'm on a fresh system and I don't remember all the configs I made.)

Is it under Model -> Model Options... -> Diagram -> Default Stroage Engine? This option is set in the model to InnoDB.

Tables without an Engine set are being treated as unable to support FKs.
That will be changed, but meanwhile, a workaround would be to explicitly set 
the tables to InnoDB

Actually the more comfortable workaround is not to use 5.2.37...

Fixed as of 5.2.38:

Tables without an engine set were treated as though they were
unable to support foreign keys. Therefore, the foreign key
declaration would be missing after forward engineering these
tables.

A workaround is to explicitly set the table engine to InnoDB.

Does the fix also work when "Server Default" is set and the model or global option is set to InnoDB for example?