- Task
- Version · 5.2.1
- User guide
ChangeDropTableWarn
Last updated: July 13, 2026
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 data loss.
Uses
Liquibase version required | 4.5.0+ |
Scope (--checks-scope) | changelog |
Default status | enabled |
Default severity (exit code) | 0 ("INFO") |
Customizable settings | No (static) |
Use the check to warn when a table is being dropped. A table drop can lead to a schema change which can potentially destroy your organization's most essential resource: critical data. Such an unintended change can result in permanent data loss, production level service outages, and more. This policy check, like other checks, can be configured with a “severity” level which returns an exit code designed to stop automated jobs, giving your team time to inspect these changes.
Before you begin
Ensure that the
--checks-scopeparameter includes the scope of this check.
Changelog checks prerequisites
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>
To run the check, use the checks run command.
Note: For flow files you'll need to run liquibase flow to apply your changes.
Example output
Short Name | Category | Description | Customization | Status | Severity | Scope | Type |
|---|---|---|---|---|---|---|---|
ChangeDropTableWarn | Data Protection | Warns when DROP TABLE is detected, providing a safety checkpoint to confirm the deletion is intentional and prevent accidental data loss from removing important or referenced tables. | <None> | enabled | 0 | changelog | sql, xml, yaml, json |
Liquibase command 'checks show' was executed successfully.