Hi all,
I have imported and then modified a database schema into MySQL Workbench EER, It's very simple. Couple of tables and a few indexes. I have then created relationships identifying primary/foreign key matches in the EER diagram.
If a generate a 'forward engineer' sql script the contraints are created as part of the CREATE TABLE command.
However, when I synchronise the EER diagram with the database these foreign keys are created as standard indexes as part of the ALTER TABLE command. Constraints are not created in the SQL.
Can I make MySQL Workbench generate the SQL to create constraints? (I am using InnoDB). Or is this a limitation?
Thanks
Kevin
I have imported and then modified a database schema into MySQL Workbench EER, It's very simple. Couple of tables and a few indexes. I have then created relationships identifying primary/foreign key matches in the EER diagram.
If a generate a 'forward engineer' sql script the contraints are created as part of the CREATE TABLE command.
However, when I synchronise the EER diagram with the database these foreign keys are created as standard indexes as part of the ALTER TABLE command. Constraints are not created in the SQL.
Can I make MySQL Workbench generate the SQL to create constraints? (I am using InnoDB). Or is this a limitation?
Thanks
Kevin