Hi,

SchemaExport may choose an order for table drops which can result in failure due foreign key constraints.

Assume there exists table category and table item. Table item has category_id as a foreign key. SchemaExport may attempt to drop table category before table item which fails. MySQL, for example will complain of ERROR 1217: Cannot delete or update a parent row: a foreign key constraint fails.

Is there any way to control the order in which SchemaExport drops tables? or maybe it could be a little smarter in choosing the order itself?

Alex

I'm having exactly the same problem with PostgreSQL. Is there any workaround available? Is this feature planned to be implemented in the future?


-Jouni Hartikainen

I've got around this by adding :

if(dialect instanceof MySQLDialect){
script.add("SET FOREIGN_KEY_CHECKS=0");
}

to generateDropSchemaScript() in net.sf.hibernate.cfg.Configuration and rebuilding Hibernate. Any chance a getDropSchemePrelude() method or similar could be added to the Dialect class and of course to the MySQL dialect?