future-rollback-count-sql

The future-rollback-count-sql command generates the SQL that Liquibase would use to sequentially revert the number of changes associated with undeployed changesets, which are added to a changelog file.

Uses

The future-rollback-count-sql command is typically used to inspect the SQL before rolling back the number of changesets that you have not deployed to your database but added to your changelog. The command shows the output starting with the most recent changes until the value specified is reached.

It is best practice to inspect SQL, which Liquibase would run when using the rollback command so you can review any changes the command would make to your database.

Running the future-rollback-count-sql command

To run the future-rollback-count-sql command, specify the driver, classpath, and URL in the Liquibase properties file. For more information, see Create and Configure a liquibase.properties File. You can also specify these properties in your command line.

Then run the future-rollback-count-sql command:

liquibase --changelog-file=dbchangelog.xml future-rollback-count-sql 2

Note: Enter the name of the changelog and the number of changesets you want to use in place of dbchangelog.xml and 2.

future-rollback-count-sql global attributes

Tip: For best results, specify all commands and parameters in the --kebab-case format in the CLI. If your preference is camelCase, it also works in the CLI.

Attribute Definition Requirement
--changelog-file

The root changelog

Required
--url

The JDBC database connection URL

Required
--username

The database username

Required
--password

The database password

Required
--output-file*

Specifies the file path to where the SQL output will be written

Optional

* If not specified, the future-rollback-count-sql output goes to STDOUT.

Note: The username and password attributes are not required for connections and systems which use alternate means of authentication.

future-rollback-count-sql command attributes

Attribute Definition Requirement
<value>

Integer specifying how many changes Liquibase applies the command to

Required

future-rollback-count-sql example output

When successful, the future-rollback-count-sql command produces the following output:

-- *********************************************************************
-- SQL to roll back currently unexecuted changes
-- *********************************************************************
-- Change Log: dbchangelog.xml
-- Ran at: 3/11/21 1:02 PM
-- Against: SCHEMA1@jdbc:oracle:thin:@localhost:1521:ORCL
-- Liquibase version: 4.1.1
-- *********************************************************************
-- Lock Database
UPDATE SCHEMA1.DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = 'WIN-20E107KB4TN (172.30.3.88)', 
LOCKGRANTED = TO_TIMESTAMP('2021-03-11 13:02:26.103', 'YYYY-MM-DD HH24:MI:SS.FF') WHERE ID = 1 AND LOCKED = 0;
-- Rolling Back ChangeSet: dbchangelog.xml::89::liquibase
DROP TABLE SCHEMA1.table34558223;
DELETE FROM SCHEMA1.DATABASECHANGELOG WHERE ID = '89' AND AUTHOR = 'liquibase' AND FILENAME = 'dbchangelog.xml';
-- Rolling Back ChangeSet: dbchangelog.xml::88::liquibase
DROP TABLE SCHEMA1.table3455822;