TableColumnLimit
Last updated: July 14, 2025
The TableColumnLimit check allows you to ensure that no table described in a changelog or existing in a database target has more than a threshold number of columns.
Uses
Property | Value |
Liquibase version required | 4.5.0+ |
Scope (--checks-scope) | changelog, database |
Default status | enabled |
Default severity (exit code) | 0 ("INFO") |
Customizable settings | Yes (dynamic) |
Use the check to validate that the target tables do not contain more than the allowed number of columns. This gives users more control over the table column count which can be between 1 and 50.
Before you begin
Ensure that you have correctly specified your Liquibase Pro license key.
Ensure that the
--checks-scopeparameter includes the scope of this check.
Changelog checks prerequisites
--license-key=<string>
--checks-scope=<string>Procedure
Enable
This check is enabled by default. To verify that it is currently enabled, run the checks show command:
liquibase checks show --check-name=<string>
Customize
This check is dynamic, meaning you can customize its settings. See the table on this page for more information.
1. Once you've enabled the check, follow the steps in the CLI to set new values.
Default values are shown in[brackets]. You can use these by pressingEnter. Alternatively, specify custom values. If a customization setting does not have a default value, you must specify custom values.
2. When finished, verify that your configuration is correct by running thechecks showcommand.
liquibase checks show --check-name=<string>
3. If you need to make any other changes, run thechecks customizecommand:
liquibase checks customize --check-name=<string>
Note: If you want to create another variant of this check with different settings, use thechecks copycommand to create a copy of the original check and then use thechecks customizecommand to customize it.
Run
To run the check, use the checks run command.
liquibase checks run --check-name=<string>