Foreign Key constraints duplicated when dbCreate='update' is set in Grails -------------------------------------------------------------------------- Key: HBX-1143 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1143 Project: Hibernate Tools Issue Type: Bug Environment: Linux, Mac Reporter: Fabrizio D'Ammassa Attachments: testFK.tar.gz If I create a foreign key constraint manually with and sql query and then I run grails with 'dbCreate=update' set, it will create another foreign key constraint. In the attached application you can find a sql folder with the schema.sql file you have to run on your mysql server. You have to change the datasource params (dbname, dbhost, dbuser, dbpassword) but leave the dbCreate option set to 'update' to reproduce the bug. After the first grails run-app you should see a duplicate constraint on your db schema (if for example you can try to export your db schema with phpmyadmin). Thanks Fabrizio -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira