Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-4123

HHH-5131 SchemaExport drop fails if constraint names change

    XMLWordPrintable

    Details

    • 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
    • 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

      Description

      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

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                rrajesh Rajesh Rajasekaran
                Reporter:
                stliu Strong Liu
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: