`rollback-count-sql`

The rollback-count-sql command is a helper command that allows you to inspect the SQL Liquibase will run while using the rollback-count command.

Uses

The rollback-count-sql command is used when you want to inspect the raw SQL before running the rollback-count command, so you can correct any issues that may arise before running the command. Liquibase uses the raw SQL to revert any changesets between the most recent and the value you specified.

Syntax

Before running the rollback-count-sql command, you can run the history command to see all your previously executed changes.

Note: rollback-countSQL works from the bottom of the list towards the top. Also, unlike the rollback-count command, there is no impact of this command. See the rollback-count topic for more information.

To run the 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 rollback-count-sql command:

liquibase 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`	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
`--change-exec-listener-class`	Fully-qualified class which specifies a ChangeExecListener	Optional
`--change-exec-listener-properties-file`	Path to a properties file for the `ChangeExecListenerClass`	Optional
`--contexts`	Specifies the changeset contexts to match. Contexts are expressions you can add to changesets to control which changesets are executed in any particular migration run.	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 changeset 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
`--rollback-script`	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 is automatically generated by Liquibase.	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

* Liquibase checks the changelog and any nested changelogs for the definitions of the changesets to roll back.

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

Liquibase Community 4.9.1 by Liquibase
-- *********************************************************************
-- Rollback 1 Change(s) Script
-- *********************************************************************
-- Change Log: example-changelog.sql
-- Ran at: 5/6/22, 12:03 PM
-- Against: DBUSER@jdbc:h2:tcp://localhost:9090/mem:dev
-- Liquibase version: 4.9.1
-- *********************************************************************

-- Lock Database
UPDATE PUBLIC.DATABASECHANGELOGLOCK SET LOCKED = TRUE, LOCKEDBY = 'DESKTOP-SQVSSV2 (192.168.1.179)', LOCKGRANTED = NOW() WHERE ID = 1 AND LOCKED = FALSE;

-- Release Database Lock
UPDATE PUBLIC.DATABASECHANGELOGLOCK SET LOCKED = FALSE, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

Liquibase command 'rollback-count-sql' was executed successfully.