Copy to clipboard

ExecuteImmediateWarning

ExecuteImmediateWarning is a custom policy check that warns you if any EXECUTE IMMEDIATE statements are detected.

regex: [\t\n\r\s]*(?i:execute)[\t\n\r\s]*(?i:immediate\s)

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+
Python 3.10.14+
Configure a valid Liquibase Pro license key
Create a Check Settings file
Ensure the Liquibase Checks extension is installed. In Liquibase 4.31.0+, it is already installed in the /liquibase/internal/lib directory, so no action is needed.
If the checks JAR is not installed, download liquibase-checks-<version>.jar and put it in the liquibase/lib directory.
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=SqlUserDefinedPatternCheck

Give your check a short name for easy identification

Use up to 64 alpha-numeric characters only.

CreateTableWithCertainColumnRequiresTrigger

Set 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.