rollback-one-update-sql

Note: This is a Liquibase Pro feature, so you need a Liquibase Pro License Key to use it.

The rollback-one-update-sql command is a helper command that allows you to inspect the SQL Liquibase will run to revert all changeset associated with the deploymentID specified in the rollback-one-update command. It is only available for Liquibase Pro users.

Uses

The rollback-one-update-sql command is typically used when you want inspect the raw SQL that Liquibase uses to revert all changesets associated with a specified deploymentId when you run the rollback-one-update command, so you don't unintentionally make a mistake.

Syntax

Before running the rollback-one-update-sql command, you can get the optional deploymentId of the changeset group you want to revert by running the history command.

Then run the rollback-one-update-sql command, with your information:

liquibase rollback-one-update-sql --changelog-file=example-changelog.xml --deploymentId=2068379006            

Note: Unlike the rollback-one-update command, there is no impact to the DATABASECHANGELOG table.

For more command-specific help, type liquibase rollback-one-update-sql --help into the command prompt.

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.

Parameter Definition Requirement
--license-key

Your Liquibase Pro license key

Required
--output-file

File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.

Optional

rollback-one-update-sql command attributes

Parameter Definition Requirement
--changelog-file *

The root changelog

Required
--url

The JDBC database connection URL. See Using JDBC URL in Liquibase.

Required
--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
--deployment-id

Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.

Optional
--driver

The JDBC driver class

Optional
--driver-properties-file

The JDBC driver properties file

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 changeset 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.

Like what you see? Try this command in Pro for Free.

Related links