We're updating the issue view to help you get more done. 

Generated drop script does not remove constraints

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

Status

Assignee

Unassigned

Reporter

Niko Wittenbeck

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Affects versions

4.2.1

Priority

Major