[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-180) SchemaExport drop broken for Postgresql

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 12 Jul 2003 1:05 AM

Done.

(The proposed "sorting" is impossible, in general. It only works if there are no circularities, which is unusual.)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-180


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-180
    Summary: SchemaExport drop broken for Postgresql
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
   Fix Fors:
             2.0.2
   Versions:
             2.0 final

   Assignee: 
   Reporter: Chris Nokleberg

    Created: Thu, 10 Jul 2003 10:45 PM
    Updated: Sat, 12 Jul 2003 1:05 AM

Description:
Since PostgreSQLDialect.getCascadeConstraintsString was changed to return "", it is now necessary for dropConstraints to return true.

Alternatively, Configuration.generateDropSchemaScript should sort the tables by foreign key constraints and drop in the correct order, avoiding any need to cascade.



---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira