-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 4.2.0.GA_CP08, 4.3.0.GA_CP07, EAP 5.0.1.CR1, EAP 5.0.1.CR2, EAP 5.0.1, 4.2.0.GA_CP09, 4.3.0.GA_CP08
-
Fix Version/s: EAP_EWP 5.1.0, 4.3.0.GA_CP09, 4.2.0.GA_CP10
-
Component/s: Hibernate
-
Labels:None
-
Environment:
PostgreSQL
-
Affects:Release Notes
-
Release Notes Text:PostgreSQL failed to drop <literal>SchemaExport</literal> if constraint names changed, causing constraint errors. Hibernate now issues a cascade when it attempts to drop a table, fixing the issue.
-
Release Notes Docs Status:Documented as Resolved Issue
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
the fix for this issue is that hibernate issues a cascade when it tries to drop a table
