While I noted that backwards compatibility was mentioned in the bugzilla entries, this is a real pain. Now if mappings are updated on a pre-existing DB, Hibernate generates a new form of the FK constraint name, fails to drop it (because it doesnt exist) and then fails to execute the new add constraint since an existing constraint exists on the same columns, just by a different name.