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: ‘dropTrigger’

Drop trigger

Available Attributes

NameDescriptionRequired ForSupportsSince
catalogNameName of the catalogdb2, db2z, oracle, postgresql
schemaNameName of the schemaall
scopeall
tableNameName of the tableall
triggerNameallall
<changeSet author="liquibase-docs" id="dropTrigger-example">
    <pro:dropTrigger catalogName="cat"
            schemaName="public"
            scope="A String"
            tableName="person"
            triggerName="A String"/>
</changeSet>
changeSet:
  id: dropTrigger-example
  author: liquibase-docs
  changes:
  - dropTrigger:
      catalogName: cat
      schemaName: public
      scope: A String
      tableName: person
      triggerName: A String
{
  "changeSet": {
    "id": "dropTrigger-example",
    "author": "liquibase-docs",
    "changes": [
      {
        "dropTrigger": {
          "catalogName": "cat",
          "schemaName": "public",
          "scope": "A String",
          "tableName": "person",
          "triggerName": "A String"
        }
      }]
    
  }
}

SQL Generated From Above Sample (SQL Server)

DROP TRIGGER [public].[A String];

Database Support

DatabaseNotesAuto Rollback
DB2SupportedNo
DB2SupportedNo
DerbyNot SupportedNo
FirebirdNot SupportedNo
H2Not SupportedNo
HyperSQLNot SupportedNo
INGRESNot SupportedNo
InformixNot SupportedNo
MariaDBNot SupportedNo
MySQLNot SupportedNo
OracleSupportedNo
PostgreSQLSupportedNo
SQL ServerSupportedNo
SQLiteNot SupportedNo
SybaseNot SupportedNo
Sybase AnywhereNot SupportedNo