[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5073?page=c...
]
Strong Liu resolved HHH-5073.
-----------------------------
Assignee: Strong Liu
Resolution: Rejected
hibernate can't know if the target DB is a fresh db, and this drop error doesn't
affect anything
SchemaExport tries to drop foreign key for non-existent table
-------------------------------------------------------------
Key: HHH-5073
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5073
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.0-Final
Environment: Windows / MySQL
Reporter: wavemaker
Assignee: Strong Liu
We execute SchemaExport in our java program to export a new database to mysql. The DDL
SchemaExport generates always contains statements to drop foreign keys (eg. alter table
cbusermgntdb.Users drop foreign key FK4E39DE8F69B1523;) on the top and it causes an error
message (eg. Table 'cbusermgntdb.users' doesn't exist) to be returned.
The DDL should not include the "drop foreign key" statements for new tables.
--
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