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.

Syntax

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 future-rollback-count-sql --count=2 --changelog-file=example-changelog.xml

Note: The --count=myCount syntax was added in Liquibase 4.4. If you use an older version, specify your count as a positional argument: <command> myCount.

Global arguments

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
--output-file	File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.	Optional

Command arguments

Attribute	Definition	Requirement
--changelog-file	The root changelog	Required
--count	Integer specifying how many changes Liquibase applies the command to. Specify as --count=myCount. Positional format <command> <count> deprecated in 4.4+.	Required
--url	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
--context-filter	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax --contexts instead of --context-filter.	Optional
--default-catalog-name	Name of the default catalog to use for the database connection	Optional
--default-schema-name	Name of the default schema to use for the database connection. If defaultSchemaName is set, then objects do not have to be fully qualified. This means you can refer to just mytable instead of myschema.mytable. Tip: In Liquibase v4.23.0+, camelCase for defaultSchemaName works successfully. If you are on an earlier version, camelCase may not work as expected. Note: The syntax liquibase.command.defaultSchemaName is valid for v4.19.0+. For prior versions, use defaultSchemaName.	Optional
--driver	The JDBC driver class	Optional
--driver-properties-file	The JDBC driver properties file	Optional
--label-filter	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
--output-default-catalog	Control whether names of objects in the default catalog are fully qualified or not. If true, they are. If false, only objects outside the default catalog are fully qualified Default: true.	Optional
--output-default-schema	Control whether names of objects in the default schema are fully qualified or not. If true, they are. If false, only objects outside the default schema are fully qualified Default: true.	Optional
--password	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
--username	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

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.

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;