Issue Type: Bug Bug
Affects Versions: 4.2.1
Assignee: Unassigned
Components: core
Created: 16/May/13 4:43 AM
Description:

I've just discovered that when using

SchemaExport export = new SchemaExport(conf);
export.drop(false, true);

generates random foreign key constraint values to drop and does not use the constraints that are existing in the database. This means that I cannot drop the db anymore, so I had to move back to Hibernate 4.2.0.

Test case:
use random existing DB, try to execute drop script and you will receive sql errors while removing constraints.

Environment: 4.2.1, MySQL 5.5
Project: Hibernate ORM
Priority: Major Major
Reporter: Nikolaus Wittenbeck
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira