futureRollbackCountSQL <value> command

The futureRollbackCountSQL <value> 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.


The futureRollbackCountSQL <value> 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 futureRollbackCountSQL <value> command

To run the futureRollbackCountSQL <value> command, you can specify the driver, classpath, and URL in your liquibase.properties file. For more information, see Creating and configuring a liquibase.properties file. You can also specify these properties in your command line.

Then run the futureRollbackCountSQL <value> command:

liquibase --changeLogFile=dbchangelog.xml futureRollbackCountSQL 2

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

futureRollbackCountSQL <value> global attributes

Attribute Definition Requirement
--changeLogFile The root changelog Required
--url The JDBC database connection URL Required
--username The database username Required
--password The database password Required
--outputFile* The file path to where the rollback SQL will be written Optional

* If not specified, the futureRollbackCountSQL output goes to STDOUT.

futureRollbackCountSQL <value> command attributes

Attribute Definition Requirement
<value> The integer indicating the number of changes Liquibase would use to roll back Required