Generate migration in Entity Modeler tries to create constraints too early
--------------------------------------------------------------------------
Key: WOL-868
URL: http://issues.objectstyle.org/jira/browse/WOL-868
Project: WOProject/WOLips
Issue Type: Bug
Components: wolips
Reporter: Mitchell Smith
Priority: Minor
The output from generate migration causes errors when run due to constraints being created on non-existent tables.
In my current project I have a number of entities with various relationships to each other, and I generated a migration for the entire model to populate the new database.
When the migration ran it failed due to foreign keys being created for tables which had not yet been added.
I noted when I ran Generate SQL that it first creates the tables, then does a number of alter table statements at the end to add the foreign keys.
It might be worth getting the generate migration to group all the constraints at the end as above to avoid this problem.
When I manually moved the constraints to the end of the update the migration executed perfectly.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
This archive was generated by hypermail 2.0.0 : Wed Jul 23 2008 - 01:03:07 EDT