tableColumnNameSize

tableColumnNameSize is a custom policy check that ensures all tables and column names are under a maximum size.

Learn how to create and customize the tableColumnNameSize Liquibase Custom Policy Check using a Python script.

This example works for relational databases. You can use this check as it is or customize it further to fit your needs in your SQL database.

For a conceptual overview of this feature, see Liquibase Pro Custom Policy Checks.

Before you begin

Scope	Database
database	Relational

Before you begin

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.

Add this code to your Checks Settings file:

tableColumnNameSize Quotes Python Script

# # #
# # # This script ensures all tables and column names are under a maximum size
# # #
# # # Notes:
    # # #

# # #
# # # Helpers come from Liquibase
# # #
import sys
import liquibase_utilities

# # #
# # # Retrieve log handler
# # # Ex.liquibase_logger.info(message)
# # #
liquibase_logger = liquibase_utilities.get_logger()

# # #
# # # Retrieve status handler
# # #
liquibase_status = liquibase_utilities.get_status()

# # #
# # # Retrieve database object
# # #
database_object = liquibase_utilities.get_database_object()

# # #
# # # Retrive maximum size from check definition
# # #
max_size = int(liquibase_utilities.get_arg("MAX_SIZE"))

# # #
# # # Check column and table names
# # #
if liquibase_utilities.is_column(database_object) or liquibase_utilities.is_table(database_object):
    object_name = database_object.getName()
object_type = database_object.getObjectTypeName()
else:
    liquibase_status.fired = False
liquibase_logger.info("Object not table or column. Check skipped.")
sys.exit(1)

# # #
# # # Check size
# # #
if len(object_name) > max_size:
    liquibase_status.fired = True
status_message = str(liquibase_utilities.get_script_message()).replace("__OBJECT_TYPE__", object_type)
status_message = status_message.replace("__OBJECT_NAME__", f "\"{object_name}\"")
status_message = status_message.replace("__CURRENT_SIZE__", str(len(object_name)))
liquibase_status.message = status_message
sys.exit(1)

# # #
# # # Default
return code
# # #
False

Initiate the customization process

In the CLI, run this command:

liquibase checks customize --check-name=CustomCheckTemplate

The CLI prompts you to finish configuring your file. A message displays:

This check cannot be customized directly because one or more fields does not have a default value.

Liquibase will then create a copy of CustomCheckTemplate and initiate the customization workflow.

Give your check a short name so you can easily identify what Python script it is associated with

Use up to 64 alpha-numeric characters only.

In this example we will name the check:

tableColumnNameSize

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 SCRIPT_DESCRIPTION

In this example, we will set the description to:

This script checks to see if all tables and column names are under a maximum size.

Set the SCRIPT_SCOPE

In this example, we will set the scope to:

database: If your check looks for the presence of keys, indexes, or table name patterns in your database schema including Liquibase Tracking Tables. With this value, the check runs once for each database object.

Set the SCRIPT_MESSAGE

For example, if you specify MAX_SIZE=10 in the CLI, you can retrieve it in your code with a variable: max_size = int(liquibase_utilities.get_arg("MAX_SIZE")).AGE. This message will display when the check is triggered.

Name of __OBJECT_TYPE__ __OBJECT_NAME__ is __CURRENT_SIZE__ characters.

Set the SCRIPT_PATH

This is the relative path where your script is stored in relation to the changelog specified in --changelog-file, whether it is stored locally or in a repository.

In this example, we will set the path to:

scripts/table-column-name-size.py.

Set the SCRIPT_ARGUMENT to MAX_SIZE=10

This allows you to pass dynamic information into the Custom Policy Check without modifying the Python code.

max_size = liquibase_utilities.get_arg("MAX_SIZE")

If you customize your check later, you can specify a new value in the CLI. If you don't need dynamic arguments, leave this field blank.

Set the REQUIRES_SNAPSHOT

If your script scope is changelog, set whether the check requires a database snapshot. Specify true if your check needs to inspect database objects.

If your script scope is database, Liquibase always takes a snapshot, so this prompt does not appear.

Note: The larger your database, the more performance impact a snapshot causes. If you cannot run a snapshot due to memory limitations, see Memory Limits of Inspecting Large Schemas.