rollback-one-changeset-sql
Last published July 28, 2025
Note: This is a Liquibase Pro feature, so you need a Liquibase Pro License Key to use it.
The rollback-one-changeset-sql command is a helper command that allows you to inspect the SQL Liquibase will run to revert the changeset specified in the rollback-one-changeset command. It is only available for Liquibase Pro users.
Uses
The rollback-one-changeset-sql
command is useful when you want to inspect the raw SQL that Liquibase uses to revert your changeset when you run the rollback-one-changeset
command, so that you don't unintentionally make a mistake.
Syntax
Before running the rollback-one-changeset-sql
command, gather the following information from your DATABASECHANGELOG table or by running the history command:
The author of the changeset you want to revert.
The ID of the changeset that you want to revert.
The file path and name of the changeset that you want to revert.
Then run the rollback-one-changeset-sql
command, with your information:
liquibase rollback-one-changeset-sql --changelog-file=example-changelog.xml --changeset-author="LiquibaseProUser" --changeset-id="createProc-proschema" --changeset-path=changelog.xml
For more command-specific help, type liquibase rollback-one-changeset-sql --help
into the command prompt.
Note: The username
and password
attributes are not required for connections and systems which use alternate means of authentication. Also, you can specify database credentials as part of the url
attribute.
Parameters
Global parameters
Attribute | Definition | Requirement |
| Your Liquibase Pro license key | Required |
| File path to where the command output will be written. If not specified, output goes to | Optional |
Command parameters
Attribute | Definition | Requirement |
| The root changelog | Required |
| The name of the author for the changeset. Supports | Required |
| The changeset ID from the changelog. | Required |
| The path to the changelog containing the changeset you want to target. For example, you may have a root changelog (root.sql) and a child changelog (child.sql). To target a specific changeset in child.sql, specify --changeset-path=child.sql. If root.sql uses include, includeAll, or sqlFile to reference child.sql, you must also specify --changelog-file=root.sql (file and path are different). If root.sql does not reference child.sql, you must also specify --changelog-file=child.sql (file and path are the same). If you only have one changelog, then --changelog-file and --changeset-path must also be the same. | Required |
| The JDBC database connection URL. | Required |
| Name of the default catalog to use for the database connection | Optional |
| Name of the default schema to use for the database connection. If Note: In the properties file and Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set | Optional |
| The JDBC driver class | Optional |
| The JDBC driver properties file | Optional |
| Control whether names of objects in the default catalog are fully qualified or not. If | Optional |
| Control whether names of objects in the default schema are fully qualified or not. If | Optional |
| Password to connect to the target database. Tip: It is best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. | Optional |
| The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates. | Optional |
| Username to connect to the target database. Tip: It is best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. | Optional |
Output
When successful, the rollback-one-changeset-sql
command produces the following output:
Liquibase Version: 4.9.1
Liquibase Pro 4.9.1 by Liquibase licensed to Liquibase Pro Evaluation until Tue Jun 07 18:00:00 MDT 2022
WARNING! Your license will expire in 29 days!
To renew Liquibase Pro please contact sales@liquibase.com or go to https://www.liquibase.org/download
rollback-one-changeset executed for DBUSER@jdbc:h2:tcp://localhost:9090/mem:dev
-- Lock Database
UPDATE PUBLIC.DATABASECHANGELOGLOCK SET LOCKED = TRUE, LOCKEDBY = 'DESKTOP-SQVSSV2 (192.168.1.179)', LOCKGRANTED = NOW() WHERE ID = 1 AND LOCKED = FALSE;
-- *********************************************************************
--rollback changeset 'example-changelog.sql::1::your.name'
-- *********************************************************************
-- Change Log: example-changelog.sql
-- Ran at: 5/10/22, 4:31 PM
-- Against: DBUSER@jdbc:h2:tcp://localhost:9090/mem:dev
-- Liquibase version: 4.9.1
-- *********************************************************************
-- Rolling Back ChangeSet: example-changelog.sql::1::your.name
DROP TABLE person;
DELETE FROM PUBLIC.DATABASECHANGELOG WHERE ID = '1' AND AUTHOR = 'your.name' AND FILENAME = 'example-changelog.sql';
-- Release Database Lock
UPDATE PUBLIC.DATABASECHANGELOGLOCK SET LOCKED = FALSE, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;
Liquibase command 'rollback-one-changeset-sql' was executed successfully.