dropTrigger
Note: This is a Liquibase Pro Change Type, so you need a Liquibase Pro License Key to use it.
Drops an existing package body.
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:
Add the Change Type to your changeset, as shown in the examples on this page.
Specify any required attributes. Use the table on this page to see which ones your database requires.
Deploy your changeset by running the
updatecommand:liquibase update
Now, you should see that the trigger you've specified is removed.
Available attributes
Name | Description | Required for | Supports | Since |
| Name of the catalog | db2, db2z, oracle, postgresql | ||
| Name of the schema | all | ||
| Name of the module for a trigger | all | ||
| Name of the table | all | ||
| Name of the trigger | all | all |
Database support
Database | Notes | |
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 |
dropTrigger examples
--liquibase formatted sql
--changeset liquibase-docs:dropTrigger-example
DROP TRIGGER [public].[A String]