UppercaseTableNames

Last updated: January 30, 2026

UppercaseTableNames is a custom policy check that looks for table names that are uppercase. If Liquibase Pro detects a table that is not uppercase, it will return the code set in step 3.

regex: (?im)create\s*(or\s*replace\s*|)table\s*((?-i).*[a-z].*)\s*\(

Before you begin

Scope

Database

changelog

Relational

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

1

Run this command in the CLI:

liquibase checks customize --check-name=SqlUserDefinedPatternCheck
2

Give your check a short name for easy identification

Use up to 64 alpha-numeric characters only.

In this example we will use:
noSelectStar
3

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

4

Set the SEARCH_STRING to this valid regular expression:

In this example we will use:
(?i:select \*)
5

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:
Table names should be UPPERCASE.
6

Set STRIP_COMMENTS to true if you want to remove the comments from the output.

Results

The regex custom policy check is created successfully.

Sample failing scripts

DELETE FROM table_name WHERE condition;

UPDATE DATABASECHANGELOGHISTORY SET column1 = value1, column2 = value2, ... WHERE condition;

DROP TABLE DATABASECHANGELOGlock;

Sample error message

CHANGELOG CHECKS ---------------- Checks completed validation of the changelog and found the following issues: Check Name:         Check for specific patterns in sql (ForbidDBCLKeyword) Changeset ID:       myChangeset Changeset Filepath: root_changelog.xml Check Severity:     BLOCKER (Return code: 4) Message:            A match for regular expression (?i)databasechangelog was detected in Changeset myChangeset.