reset
Note: This is a Liquibase Pro feature, so you need a Liquibase Pro License Key to use it.
The reset subcommand reverts customizations made to the check indicated in the --check-name parameter to the original configuration.
Uses
You can typically use the reset command to return to a reliable starting state when working with checks. This subcommand does not affect static checks and uncustomized dynamic checks.
When you reset a dynamic check that has been customized multiple times, the check will be reverted to default settings and not to the previous customized settings.
Note: To view a list of available checks, run liquibase checks show.
Syntax
The command is interactive, and you need to follow the CLI output messages to execute it:
-
Run the command specifying your values:
liquibase checks reset --check-name=TableColumnLimitNote: If you have a checks settings file customized for a specific environment or project, you need to pass that using the
--checks-settings-fileparameter. If you do not include this parameter, Liquibase uses the default settings file:liquibase.checks-settings.conf. See Use the Checks Settings Configuration File. - Confirm the change. The command updates the check in the checks settings file.
Parameters
Global parameters
| Attribute | Definition | Requirement |
|---|---|---|
|
|
Your Liquibase Pro license key |
Required |
Command parameters
| Parameter | Description | Requirement |
|---|---|---|
|
|
The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the |
Required |
|
|
Automatically enable new policy checks in |
Optional |
|
|
Allows automatic backup and updating of the |
Optional |
|
|
Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. For more information, see Use the Checks Settings Configuration File. |
Optional |
Global parameters
| Attribute | Definition | Requirement |
|---|---|---|
|
|
Your Liquibase Pro license key |
Required |
Command parameters
| Parameter | Description | Requirement |
|---|---|---|
|
|
The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the |
Required |
|
|
Automatically enable new policy checks in |
Optional |
|
|
Allows automatic backup and updating of the |
Optional |
|
|
Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. For more information, see Use the Checks Settings Configuration File. |
Optional |
Global parameters
| Attribute | Definition | Requirement |
|---|---|---|
|
|
Your Liquibase Pro license key |
Required |
Command parameters
| Parameter | Description | Requirement |
|---|---|---|
|
|
The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the |
Required |
|
|
Automatically enable new policy checks in |
Optional |
|
|
Allows automatic backup and updating of the |
Optional |
|
|
Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. For more information, see Use the Checks Settings Configuration File. |
Optional |
Global parameters
| Attribute | Definition | Requirement |
|---|---|---|
|
|
Your Liquibase Pro license key |
Required |
Command parameters
| Parameter | Description | Requirement |
|---|---|---|
|
|
The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the |
Required |
|
|
Automatically enable new policy checks in |
Optional |
|
|
Allows automatic backup and updating of the |
Optional |
|
|
Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. For more information, see Use the Checks Settings Configuration File. |
Optional |
Global parameters
| Attribute | Definition | Requirement |
|---|---|---|
|
|
Your Liquibase Pro license key |
Required |
Command parameters
| Parameter | Description | Requirement |
|---|---|---|
|
|
The name of the check(s) you want to target. Comma-separated list of one or more enabled checks. Checks to exclude can be prefixed with the |
Required |
|
|
Automatically enable new policy checks in |
Optional |
|
|
Allows automatic backup and updating of the |
Optional |
|
|
Specifies the checks settings file to use with policy checks commands. Write the relative path of the settings file that you want to read from or modify. For more information, see Use the Checks Settings Configuration File. |
Optional |
reset example output
Liquibase Version: 4.28.0
Liquibase Pro 4.28.0 by Liquibase licensed to Liquibase_QA until Tue Dec 02 01:59:59 UYT 2025
WARNING: Additional checks have been added to 'liquibase.checks-settings.conf' and are disabled. To auto-enable new checks on upgrades, set '--auto-enable-new-checks=true'. Learn more at https://docs.liquibase.com/policy-checks
Resetting check with short name 'TableColumnLimit' to original configuration of its base check 'TableColumnLimit'
Current Customization Settings
Severity = BLOCKER MAX_COLUMNS = '60'
Default Settings
Severity = INFO MAX_COLUMNS = '50'
Would you like to set 'TableColumnLimit' to it's default settings? (Y/n) [Y]:
y
Reset complete. Review the table below to confirm your changes.
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| Short Name | Scope | Status | Severity | Customization | Description |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SqlGrantWarn | changelog | enabled | 1 | <None> | This check warns a user when |
| | | | | | SQL contains 'GRANT' |
| | | | | | statements so that they can |
| | | | | | ensure that the privilege |
| | | | | | being granted won't lead to |
| | | | | | security issues. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SqlRevokeWarn | changelog | enabled | 1 | <None> | This check warns a user when |
| | | | | | SQL contains 'REVOKE' |
| | | | | | statements so that they can |
| | | | | | ensure that the privilege |
| | | | | | being revoked won't lead to |
| | | | | | data access and dependency |
| | | | | | issues. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| WarnOnUseDatabase | changelog | enabled | 1 | <None> | This check warns a user when |
| | | | | | generated or raw SQL contains |
| | | | | | 'USE DATABASE' directive. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ChangeDropTableWarn | changelog | enabled | 1 | <None> | This check warns a user when a |
| | | | | | table is being dropped so that |
| | | | | | they can ensure that dropping |
| | | | | | the table won't lead to |
| | | | | | unintentional loss of data. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ChangeDropColumnWarn | changelog | enabled | 1 | <None> | This check warns a user when a |
| | | | | | column is being dropped so |
| | | | | | that they can ensure that |
| | | | | | dropping the column won't lead |
| | | | | | to unintentional loss of data. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ModifyDataTypeWarn | changelog | enabled | 1 | <None> | This check warns a user when a |
| | | | | | change will result in |
| | | | | | modification of a data type so |
| | | | | | they can ensure that modifying |
| | | | | | the data type won't lead to |
| | | | | | unintentional loss of data |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SqlSelectStarWarn | changelog | enabled | 1 | <None> | This check warns a user when |
| | | | | | generated or raw SQL contains |
| | | | | | 'SELECT *' statements so that |
| | | | | | they can ensure selecting all |
| | | | | | fields from a table in a query |
| | | | | | is safe and necessary |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SqlUserDefinedPatternCheck | changelog | disabled | 1 | SEARCH_STRING = null | This check scans SQL for the |
| | | | | MESSAGE = A match for regular | presence of specific patterns |
| | | | | expression <SEARCH_STRING> was | in specified changelog paths, |
| | | | | detected in Changeset | and warns the user when they |
| | | | | <CHANGESET> in changelog path | are found. |
| | | | | <PATH_FILTER_REGEX>. | |
| | | | | STRIP_COMMENTS = true | |
| | | | | PATH_FILTER_REGEX = null | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| EndDelimiterExistsWhenPatternExists | changelog | disabled | 1 | SEARCH_STRING = null | This check triggers when a |
| | | | | CASE_SENSITIVE = true | changeset contains the |
| | | | | STRIP_COMMENTS = true | supplied pattern string or |
| | | | | MESSAGE = The pattern | regex, but does not have an |
| | | | | '<SEARCH_STRING>' was found | end delimiter set specifically |
| | | | | without an end delimiter in | in the changeset or via |
| | | | | Changeset '<CHANGESET>'. | options such as |
| | | | | | 'pro-global-end-delimiter' or |
| | | | | | 'endDelimiter' attribute in a |
| | | | | | modifyChangesets tag. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| PatternAFollowedByPatternB | changelog | disabled | 1 | PRIMARY_SEARCH_STRING = null | Check triggers if the |
| | | | | LOOKAHEAD_SEARCH_STRING = null | user-supplied regex pattern A |
| | | | | CASE_SENSITIVE = true | is followed by the |
| | | | | LOOKAHEAD_MESSAGE = Match | user-supplied regex pattern B |
| | | | | found: | |
| | | | | '<PRIMARY_SEARCH_STRING>' is | |
| | | | | followed by | |
| | | | | '<LOOKAHEAD_SEARCH_STRING>' in | |
| | | | | Changeset '<CHANGESET>'. | |
| | | | | STRIP_COMMENTS = true | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| PatternAPrecededByPatternB | changelog | disabled | 1 | PRIMARY_SEARCH_STRING = null | Check triggers if the |
| | | | | LOOKBEHIND_SEARCH_STRING = | user-supplied regex pattern A |
| | | | | null | is preceded by the |
| | | | | CASE_SENSITIVE = true | user-supplied regex pattern B |
| | | | | LOOKBEHIND_MESSAGE = Match | |
| | | | | found: | |
| | | | | '<LOOKBEHIND_SEARCH_STRING>' | |
| | | | | is preceded by | |
| | | | | '<PRIMARY_SEARCH_STRING>' in | |
| | | | | Changeset '<CHANGESET>'. | |
| | | | | STRIP_COMMENTS = true | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| PatternANotFollowedByPatternB | changelog | disabled | 1 | PRIMARY_SEARCH_STRING = null | Check triggers if the |
| | | | | LOOKAHEAD_SEARCH_STRING = null | user-supplied regex pattern A |
| | | | | CASE_SENSITIVE = true | is NOT followed by the |
| | | | | NEGATIVE_LOOKAHEAD_MESSAGE = | user-supplied regex pattern B |
| | | | | Match found: | |
| | | | | '<PRIMARY_SEARCH_STRING>' is | |
| | | | | not followed by | |
| | | | | '<LOOKAHEAD_SEARCH_STRING>' in | |
| | | | | Changeset '<CHANGESET>'. | |
| | | | | STRIP_COMMENTS = true | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| PatternANotPrecededByPatternB | changelog | disabled | 1 | PRIMARY_SEARCH_STRING = null | Check triggers if the |
| | | | | LOOKBEHIND_SEARCH_STRING = | user-supplied regex pattern A |
| | | | | null | is NOT preceded by the |
| | | | | CASE_SENSITIVE = true | user-supplied regex pattern B |
| | | | | NEGATIVE_LOOKBEHIND_MESSAGE = | |
| | | | | Match found: | |
| | | | | '<LOOKBEHIND_SEARCH_STRING>' | |
| | | | | is not preceded by | |
| | | | | '<PRIMARY_SEARCH_STRING>' in | |
| | | | | Changeset '<CHANGESET>'. | |
| | | | | STRIP_COMMENTS = true | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| TableColumnLimit | changelog, | enabled | 0 | MAX_COLUMNS = 50 | Ensures that no table has more |
| | database | | | | than a threshold number of |
| | | | | | columns. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| MaxAffectedRowsAllowedDelete | changelog | enabled | 1 | MAX_ROWS = 50 | This checks triggers when the |
| | | | | MESSAGE = <AFFECTED_ROWS> rows | Max Affected Rows Allowed |
| | | | | will be affected, which is | value is exceeded by the |
| | | | | more than the allowed | number of rows DELETED by a |
| | | | | '<THRESHOLD>' rows. The SQL | SQL statement. The SQL |
| | | | | statement is '<STATEMENT>' in | statement is executed against |
| | | | | '<CHANGESET>'. | the database, and then rolled |
| | | | | | back. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| MaxAffectedRowsAllowedInsert | changelog | enabled | 1 | MAX_ROWS = 50 | This checks triggers when the |
| | | | | MESSAGE = <AFFECTED_ROWS> rows | Max Affected Rows Allowed |
| | | | | will be affected, which is | value is exceeded by the |
| | | | | more than the allowed | number of rows INSERTED by a |
| | | | | '<THRESHOLD>' rows. The SQL | SQL statement. The SQL |
| | | | | statement is '<STATEMENT>' in | statement is executed against |
| | | | | '<CHANGESET>'. | the database, and then rolled |
| | | | | | back. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| MaxAffectedRowsAllowedUpdate | changelog | enabled | 1 | MAX_ROWS = 50 | This checks triggers when the |
| | | | | MESSAGE = <AFFECTED_ROWS> rows | Max Affected Rows Allowed |
| | | | | will be affected, which is | value is exceeded by the |
| | | | | more than the allowed | number of rows UPDATED by a |
| | | | | '<THRESHOLD>' rows. The SQL | SQL statement. The SQL |
| | | | | statement is '<STATEMENT>' in | statement is executed against |
| | | | | '<CHANGESET>'. | the database, and then rolled |
| | | | | | back. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ObjectNameMustMatch | changelog, | disabled | 1 | OPERATOR = STARTS_WITH | This check confirms the listed |
| | database | | | SEARCH_STRING = null | object names conform to the |
| | | | | OBJECT_TYPES = null | supplied pattern. |
| | | | | CASE_SENSITIVE = true | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ObjectNameMustNotMatch | changelog, | disabled | 1 | OPERATOR = STARTS_WITH | This check confirms the listed |
| | database | | | SEARCH_STRING = null | object names do not match the |
| | | | | OBJECT_TYPES = null | supplied pattern. |
| | | | | CASE_SENSITIVE = true | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SqlGrantSpecificPrivsWarn | changelog | disabled | 1 | PRIVILEGE_LIST = null | This check warns a user when |
| | | | | STRIP_COMMENTS = true | changeset includes or |
| | | | | | generates sql that grants |
| | | | | | specific privileges to a user |
| | | | | | or role |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| CheckRunInTransactionValue | changelog | enabled | 1 | RUN_IN_TRANSACTION_VALUE = | This check triggers when a |
| | | | | false | changeset contains the |
| | | | | MESSAGE = A match for regular | user-specified |
| | | | | expression <SEARCH_STRING> was | runInTransactions value of |
| | | | | detected in Changeset | 'true' or 'false'. Note: |
| | | | | <CHANGESET>. | Changesets without a |
| | | | | | runInTransactions value are |
| | | | | | not checked. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ChangeTruncateTableWarn | changelog | enabled | 1 | <None> | This check warns a user when a |
| | | | | | table is being truncated so |
| | | | | | that they can ensure that |
| | | | | | truncating the table won't |
| | | | | | lead to unintentional loss of |
| | | | | | data. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SqlGrantOptionWarn | changelog | enabled | 1 | <None> | This check warns a user when |
| | | | | | SQL contains 'GRANT' |
| | | | | | statements that include the |
| | | | | | 'WITH GRANT OPTION' clause so |
| | | | | | that they can ensure that the |
| | | | | | privilege being granted won't |
| | | | | | lead to security issues |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| OracleReservedKeywords | changelog, | disabled | 1 | OBJECT_TYPES = null | Disallow Oracle reserved |
| | database | | | ALLOWED_LIST = null | keywords from being used in |
| | | | | CASE_SENSITIVE = true | database object names. See |
| | | | | | https://docs.oracle.com/cd/B19 |
| | | | | | 306_01/em.102/b40103/app_oracl |
| | | | | | e_reserved_words.htm for |
| | | | | | complete list of keywords. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SQLServerReservedKeywords | changelog, | disabled | 1 | OBJECT_TYPES = null | Disallow SQL Server reserved |
| | database | | | ALLOWED_LIST = null | keywords from being used in |
| | | | | CASE_SENSITIVE = true | database object names. See |
| | | | | | https://docs.microsoft.com/en- |
| | | | | | us/sql/t-sql/language-elements |
| | | | | | /reserved-keywords-transact-sq |
| | | | | | l?view=sql-server-ver16 for |
| | | | | | complete list of keywords. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SQLServerFutureReservedKeywords | changelog, | disabled | 1 | OBJECT_TYPES = null | Disallow SQL Server's future |
| | database | | | ALLOWED_LIST = null | reserved keywords from being |
| | | | | CASE_SENSITIVE = true | used in database object names. |
| | | | | | See |
| | | | | | https://docs.microsoft.com/en- |
| | | | | | us/sql/t-sql/language-elements |
| | | | | | /reserved-keywords-transact-sq |
| | | | | | l?view=sql-server-ver16 for |
| | | | | | complete list of keywords. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| PostgresReservedKeywords | changelog, | disabled | 1 | OBJECT_TYPES = null | Disallow Postgres reserved |
| | database | | | ALLOWED_LIST = null | keywords from being used in |
| | | | | CASE_SENSITIVE = true | database object names. See |
| | | | | | https://www.postgresql.org/doc |
| | | | | | s/14/sql-keywords-appendix.htm |
| | | | | | l for complete list of |
| | | | | | keywords. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SQLServerODBCReservedKeywords | changelog, | disabled | 1 | OBJECT_TYPES = null | Disallow SQL Server's ODBC |
| | database | | | ALLOWED_LIST = null | reserved keywords from being |
| | | | | CASE_SENSITIVE = true | used in database object names. |
| | | | | | See |
| | | | | | https://docs.microsoft.com/en- |
| | | | | | us/sql/t-sql/language-elements |
| | | | | | /reserved-keywords-transact-sq |
| | | | | | l?view=sql-server-ver16 for |
| | | | | | complete list of keywords. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| PostgresNonReservedKeywords | changelog, | disabled | 1 | OBJECT_TYPES = null | Disallow Postgres non-reserved |
| | database | | | ALLOWED_LIST = null | keywords from being used in |
| | | | | CASE_SENSITIVE = true | database object names. See |
| | | | | | https://www.postgresql.org/doc |
| | | | | | s/14/sql-keywords-appendix.htm |
| | | | | | l for complete list of |
| | | | | | keywords. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| SqlGrantAdminWarn | changelog | enabled | 1 | <None> | This check warns a user when |
| | | | | | SQL contains 'GRANT' |
| | | | | | statements that include the |
| | | | | | 'WITH ADMIN OPTION' clause so |
| | | | | | that they can ensure that the |
| | | | | | privilege being granted won't |
| | | | | | lead to security issues |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| DetectChangeType | changelog | enabled | 1 | CHANGE_TYPE_LIST = | This check warns a user when a |
| | | | | dropTable,dropColumn | ChangeSet includes a |
| | | | | | ChangeType listed by the user |
| | | | | | as forbidden |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| RollbackRequired | changelog | enabled | 1 | <None> | This check triggers when a |
| | | | | | changeset does not have a |
| | | | | | rollback defined. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ChangesetLabelCheck | changelog | enabled | 1 | <None> | This check enforces the |
| | | | | | Liquibase recommendation that |
| | | | | | labels be assigned to each |
| | | | | | changeset to provide better |
| | | | | | deployment control and to |
| | | | | | enhance traceability of |
| | | | | | efforts across changesets. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ChangesetContextCheck | changelog | enabled | 1 | <None> | This check enforces the |
| | | | | | Liquibase recommendation that |
| | | | | | contexts be assigned to each |
| | | | | | changeset to provide better |
| | | | | | deployment control and to |
| | | | | | enhance traceability of |
| | | | | | efforts across changesets. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ChangesetCommentCheck | changelog | enabled | 1 | <None> | This check enforces the |
| | | | | | Liquibase recommendation that |
| | | | | | comments be added to each |
| | | | | | changeset to document the |
| | | | | | purpose of a changeset for |
| | | | | | other/future consumers of this |
| | | | | | changelog |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| OneChangePerChangeset | changelog | enabled | 1 | <None> | This check enforces the |
| | | | | | Liquibase Best Practice of |
| | | | | | keeping individual changesets |
| | | | | | small by limiting them to one |
| | | | | | statement or change. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| UserDefinedLabelCheck | changelog | disabled | 1 | OPERATOR = STARTS_WITH | This check confirms that a |
| | | | | SEARCH_STRING = null | specific label or a label that |
| | | | | | matches a specific pattern is |
| | | | | | present on all changesets. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| UserDefinedContextCheck | changelog | disabled | 1 | OPERATOR = STARTS_WITH | This check confirms that a |
| | | | | SEARCH_STRING = null | specific context or a context |
| | | | | | that matches a specific |
| | | | | | pattern is present on all |
| | | | | | changesets. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| PrimaryKeyOnCreateTable | changelog | enabled | 1 | EXCEPTIONS_LIST = | This check warns when a create |
| | | | | CASE_SENSITIVE = true | table action doesn't also |
| | | | | | include a primary key. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| CheckTablesForIndex | database | enabled | 1 | <None> | This check scans your target |
| | | | | | URL database tables to find |
| | | | | | tables which do not have an |
| | | | | | associated index. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| TableCommentCheck | changelog, | enabled | 1 | <None> | With database-scope, this |
| | database | | | | check flags any table which |
| | | | | | does not have a comment. With |
| | | | | | changelog-scope, this check |
| | | | | | triggers on changesets with a |
| | | | | | CREATE table changetype that |
| | | | | | does not also add a comment |
| | | | | | for the table in that same |
| | | | | | changeset. (Note: This is not |
| | | | | | a check for a Liquibase |
| | | | | | changelog comment.) |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| TableCommentPatternCheck | changelog, | disabled | 1 | OPERATOR = CONTAINS | This check triggers when |
| | database | | | SEARCH_STRING = null | specific user-supplied |
| | | | | MESSAGE = A match for regular | patterns are found in Table |
| | | | | expression <SEARCH_STRING> was | Comments. |
| | | | | detected in <IDENTIFIER>. | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ChainedChecksTemplate | changelog, | disabled | 1 | LOGIC_CONDITIONAL = null | This check triggers when the |
| | database | | | MESSAGE = The conditions in | logic conditional evaluates to |
| | | | | '<chained checks shortname>' | true |
| | | | | were met for '<logic | |
| | | | | conditional>'. The chained | |
| | | | | checks include <checknames>. | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| ConstraintMustExist | database | disabled | 1 | CONSTRAINT_OPERATOR = | Check for and alert when |
| | | | | STARTS_WITH | specified table does not |
| | | | | TABLE_NAME = null | contain the required |
| | | | | COLUMN_NAME = null | constraint(s). |
| | | | | CONSTRAINT = PRIMARYKEY | |
| | | | | CASE_SENSITIVE = true | |
| | | | | MESSAGE = The specified table | |
| | | | | '<TABLE_NAME>' does not | |
| | | | | contain the required | |
| | | | | '<CONSTRAINT>' constraint. | |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
| RequireChangesetIDisUUID | changelog | enabled | 1 | <None> | Alerts when a changeset ID |
| | | | | | does not follow the 8-4-4-4-12 |
| | | | | | pattern of UUID or GUID. |
+-------------------------------------+------------+----------+----------+--------------------------------+--------------------------------+
TIP
Test your changes by running checks against your changelog with 'liquibase checks run'
Liquibase command 'checks reset' was executed successfully.