dropTrigger

Note: This is a Liquibase Pro Change Type, so you need a Liquibase Pro License Key to use it.

The dropTrigger Change Type drops the trigger in the database.

Uses

You can typically use the dropTrigger Change Type when you want to remove an existing trigger from your database. It can include catalog, schema, and table name attributes listed in this documentation.

Running the dropTrigger Change Type

To run this Change Type, follow these steps:

  1. Add the Change Type to your changeset, as shown in the examples on this page.
  2. Specify any required attributes. Use the table on this page to see which ones your database requires.
  3. Deploy your changeset by running the update command:
    4. liquibase update

Now, you should see that the trigger you've specified is removed.

Available attributes

Name Description Required for Supports Since
catalogName

Name of the catalog

 db2, db2z, oracle, postgresql
schemaName

Name of the schema

 all
scope

Name of the module for a trigger

 all
tableName

Name of the table

 all
triggerName

Name of the trigger

 all all

Examples

--liquibase formatted sql

--changeset liquibase-docs:dropTrigger-example
DROP TRIGGER [public].[A String]
databaseChangeLog:
-  changeSet:
    id:  dropTrigger-example
    author:  liquibase-docs
    changes:
    -  dropTrigger:
        catalogName:  department
        schemaName:  public
        scope:  A String
        tableName:  person
        triggerName:  A String
{
    "databaseChangeLog": [
        {
            "changeSet": {
                "id": "dropTrigger-example",
                "author": "liquibase-docs",
                "changes": [
                    {
                        "dropTrigger": {
                            "catalogName": "department",
                            "schemaName": "public",
                            "scope": "A String",
                            "tableName": "person",
                            "triggerName": "A String"
                        }
                    }
                ]
            }
        }
    ]
}
<databaseChangeLog
    xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ext="http://www.liquibase.org/xml/ns/dbchangelog-ext"
    xmlns:pro="http://www.liquibase.org/xml/ns/pro"
    xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
        http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd
        http://www.liquibase.org/xml/ns/dbchangelog-ext
        http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-ext.xsd
        http://www.liquibase.org/xml/ns/pro
        http://www.liquibase.org/xml/ns/pro/liquibase-pro-latest.xsd">

    <changeSet  author="liquibase-docs"  id="dropTrigger-example">
        <pro:dropTrigger  catalogName="department"
            schemaName="public"
            scope="A String"
            tableName="person"
            triggerName="A String"/>
    </changeSet>

</databaseChangeLog>

Database support

Database Notes Auto Rollback
DB2/LUW Not Supported No
DB2/z Not Supported No
Derby Not Supported No
Firebird Not Supported No
Google BigQuery Supported No
H2 Not Supported No
HyperSQL Not Supported No
INGRES Not Supported No
Informix Not Supported No
MariaDB Supported No
MySQL Supported No
Oracle Supported No
PostgreSQL Supported No
Snowflake Not Supported No
SQL Server Supported No
SQLite Not Supported No
Sybase Not Supported No
Sybase Anywhere Not Supported No

Related links