The ObjectNameMustNotMatch check allows you to confirm the listed object names conform to the supplied pattern and locate the object names that do not match so they can be corrected.

  • checks require specific parameters noted in the table.
  • Customizations to checks configuration are stored in the liquibase.checks-settings file.


Use the check to validate that your object names do not fit naming conventions and that object names match the supplied pattern. This allows you to locate any object that does not match the criteria so that you can correct it. This gives you direct control over the object names and avoids naming issues.

Run the ObjectNameMustNotMatch check

To run the ObjectNameMustNotMatch check, ensure you have a Liquibase Lab license, a valid URL property that points to a live JDBC connection or a snapshot, and the checks-scope property includes database. The checks-scope is set in the default properties file, environment variable, or any standard method. Then check if any searchable object types match the supplied pattern. Enable the ObjectNameMustNotMatch check by running the following command in the CLI: 

liquibase checks enable --check-name=ObjectNameMustNotMatch

Liquibase prompts you to establish a copy of this check and to initiate the customization work flow. To do this, select options for each of the attributes below in the CLI.

Note: This check can not be enabled directly because one or more fields does not have a default value. Creating a copy of this check initiates the customization work flow.

The check is active.

ObjectNameMustNotMatch Configurable Attributes

The following table identifies attributes that are configurable by ObjectNameMustNotMatch.

Attribute Name Type Description Options/ Validation Default Value


The location to look for the provided SearchString Value

- startsWith - SearchString provided should be found at the beginning of the table.

- endsWith - SearchString provided should be found at the end of the table.

- contains - SearchString Provided can be anywhere in the table.

- regexp - SearchString provided is a regexp that should be matched.



The substring or regular expression to match.

Validation - SearchString should be a valid regular expression.




Enter the required object types, separated by commas TABLE, COLUMN, SEQUENCE, INDEX PRIMARYKEY


The message the user wishes to print when the check detects a pattern match

A match for regular expression {{SearchString}} value was detected in Changeset changeset id.


Set CASE_SENSITIVE (options: true, false) user entry of true or false is accepted case-insensitively false


Enter the required constraint(s), separate NOT NULL, UNIQUE, PRIMARYKEY, FOREIGNKEY PRIMARYKEY