Liquibase® version 3.8.2 is now available! Get it for free.
2018 XML Announcement
News 5 Ways to Fix a Bad Database Change in Liquibase
04 Dec 2019

- and/or -

All Previous Posts >>

Change: ‘dropPackage’

Drops an existing package

Available Attributes

NameDescriptionRequired ForSupportsSince
catalogNameName of the catalogall
packageNameName of the package to dropallall
schemaNameName of the schemaall
<changeSet author="liquibase-docs" id="dropPackage-example">
    <pro:dropPackage catalogName="cat"
            packageName="A String"
            schemaName="public"/>
</changeSet>
changeSet:
  id: dropPackage-example
  author: liquibase-docs
  changes:
  - dropPackage:
      catalogName: cat
      packageName: A String
      schemaName: public
{
  "changeSet": {
    "id": "dropPackage-example",
    "author": "liquibase-docs",
    "changes": [
      {
        "dropPackage": {
          "catalogName": "cat",
          "packageName": "A String",
          "schemaName": "public"
        }
      }]
    
  }
}

SQL Generated From Above Sample (MySQL)

DROP PACKAGE cat.`A String`;

Database Support

DatabaseNotesAuto Rollback
DB2SupportedNo
DB2SupportedNo
DerbySupportedNo
FirebirdSupportedNo
H2SupportedNo
HyperSQLSupportedNo
INGRESSupportedNo
InformixSupportedNo
MariaDBSupportedNo
MySQLSupportedNo
OracleSupportedNo
PostgreSQLSupportedNo
SQL ServerSupportedNo
SQLiteSupportedNo
SybaseSupportedNo
Sybase AnywhereSupportedNo