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

Enable Trigger

Available Attributes

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

SQL Generated From Above Sample (SQL Server)

ENABLE TRIGGER [public].[A String]  ON cat.[public].person;

Database Support

DatabaseNotesAuto Rollback
DB2Not SupportedYes
DB2Not SupportedYes
DerbyNot SupportedYes
FirebirdNot SupportedYes
H2Not SupportedYes
HyperSQLNot SupportedYes
INGRESNot SupportedYes
InformixNot SupportedYes
MariaDBNot SupportedYes
MySQLNot SupportedYes
OracleSupportedYes
PostgreSQLSupportedYes
SQL ServerSupportedYes
SQLiteNot SupportedYes
SybaseNot SupportedYes
Sybase AnywhereNot SupportedYes