[hibernate-issues] [Hibernate-JIRA] Created: (HHH-5131) SchemaExport drop fails if constraint names change

SchemaExport drop fails if constraint names change -------------------------------------------------- Key: HHH-5131 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5131 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.3.2 Environment: PostgreSQL Reporter: Strong Liu Fix For: 3.3.x, 3.5.x for PostgreSQL dialect, it doesn't use cascade to drop tables, this may causes error when it drops the constraints. for example, there is a table A with a FK which name is "123456" but schemaUpdate uses a different FK name to drop it, then fails, then it tries to drop Table A, fails again :( HB-540 was reported a long ago, and Gavin added a comment "We can't apply this patch since older versions of Postgres don't support the cascade syntax." but I don't think it is still a problem( it was a comment added in 2003), as even the PostgreSQL 7.x support this syntax -- 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