CreateTableWithCertainColumnRequiresTrigger
Last updated: January 30, 2026
CreateTableWithCertainColumnRequiresTrigger is a custom policy check that requires when a CREATE TABLE statement with a certain column such as SQLKEY exists, there must also be a CREATE OR REPLACE TRIGGER included.
regex: (?is)(?=.*\b(create.*table.*sqlkey\s+number)\b)(?!.*\b(create./trigger)\b).*
This example utilizes Oracle. You can use this check as it is or customize it further to fit your needs in your SQL database. All Regex Custom Policy Checks can only run against the changelog, not against the database.
Before you begin
Scope | Database |
changelog | Oracle |
Liquibase 4.29.0+
Configure a valid Liquibase Pro license key
Ensure the Liquibase Checks extension is installed. In Liquibase 4.31.0+, it is already installed in the
/liquibase/internal/libdirectory, so no action is needed.If the checks JAR is not installed, download
liquibase-checks-<version>.jarand put it in theliquibase/libdirectory.Maven users only:
Add this dependency to your pom.xml file:
<dependency>
<groupId>org.liquibase.ext</groupId>
<artifactId>liquibase-checks</artifactId>
<version>2.0.0</version>
</dependency>
Java Development Kit 17+ (available for Open JDK and Oracle JDK)
Linux, macOS, or Windows operating system
Procedure
These steps describe how to create the Custom Policy Check. It does not exist by default in Liquibase Pro.
Run this command in the CLI:
liquibase checks customize --check-name=SqlUserDefinedPatternCheckGive your check a short name for easy identification
Use up to 64 alpha-numeric characters only.
CreateTableWithCertainColumnRequiresTriggerSet the Severity to return a code of 0-4 when triggered.
These severity codes allow you to determine if the job moves forward or stops when this check triggers.
Learn more here: Use Policy Checks in Automation: Severity and Exit Code
options: 'INFO'=0, 'MINOR'=1, 'MAJOR'=2, 'CRITICAL'=3, 'BLOCKER'=4
Set the SEARCH_STRING to this valid regular expression:
Regular expression search string
(?is)(?=.*\b(create.*table.*sqlkey\s+number)\b)(?!.*\b(create./trigger)\b).*Set the MESSAGE to display when a match for the regular expression <SEARCH_STRING> is found in a Changeset.
In this example we will use:
Error! SQLKEY column requires creation of a TRIGGER. Ensure that you have a CREATE OR REPLACE TRIGGER in your changeset.Set STRIP_COMMENTS to true if you want to remove the comments from the output.
CreateTableMustHaveOneGrant
Leave the PATH_Filter_REGEX blank.
Set SPLIT_STATEMENTS to false.
Settting SPLIT_STATEMENTS to false prevents Liquibase from splitting multiple SQL statements on the delimiter or evaluating each individually.
Results
The regex custom policy check is created successfully.
Sample Passing Script
--changeset amalik:employee
CREATE TABLE EMPLOYEE (
SQLKEY NUMBER(15,0),
EMPLOYEE_ID INT NOT NULL GENERATED ALWAYS AS IDENTITY CONSTRAINT PEOPLE_PK PRIMARY KEY,
FIRST_NAME VARCHAR(26),
LAST_NAME VARCHAR(26)
);
CREATE SEQUENCE SEQ_EMPLOYEE MINVALUE 1 MAXVALUE 999999999999 INCREMENT BY 1 START WITH 1 CACHE NOORDER NOCYCLE;
Sample Failing Scripts
--changeset amalik:employee
CREATE TABLE EMPLOYEE (
SQLKEY NUMBER(15,0),
EMPLOYEE_ID INT NOT NULL GENERATED ALWAYS AS IDENTITY CONSTRAINT PEOPLE_PK PRIMARY KEY,
FIRST_NAME VARCHAR(26),
LAST_NAME VARCHAR(26)
);
Sample Error Message
CHANGELOG CHECKS
----------------
Checks completed validation of the changelog and found the following issues:
Check Name: Check for specific patterns in sql (CreateTableWithCertainColumnRequiresTrigger)
Changeset ID: PMA0087
Changeset Filepath: script1.sql
Check Severity: MAJOR (Return code: 2)
Message: Error! SQLKEY column requires creation of a TRIGGER. Ensure that you have a CREATE OR REPLACE TRIGGER in your changeset.