Documentation bug for dropTable

General Discussion
1

Hello,

the documentation for dropTable states that the attribute “cascadeConstraints” is supported for all DBMS.

At least for SQL Server this is not true

Consider the following changeLog:

  1. <?xml version="1.0" encoding="utf-8"?>
  2. http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-2.0.xsd"
  3.     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  4.     xmlns="http://www.liquibase.org/xml/ns/dbchangelog">
  7.   
  8.     
  9.         <constraints nullable="false"
  10.            primaryKey="true"
  11.            primaryKeyName="pk_bar" />
  12.     
  13.   
  15.   
  16.      
  17.      
  18.   
  20.    <addForeignKeyConstraint constraintName="fk_bar_foo"
  21.       baseTableName="foo" baseColumnNames="bar_id"
  22.       referencedTableName="bar" referencedColumnNames="id" />
  23.   
  25.  
  26.    
  27.  
The changeSet id="2" will fail with the error message:

Error executing SQL DROP TABLE [dbo].[bar]: Could not drop object ‘dbo.bar’ because it is referenced by a FOREIGN KEY constraint.

To my knowledge this only works on Postgres, Oracle, DB2, H2 and HSQLDB.