rollbackOneChangeSetSQL command


The rollbackOneChangeSetSQL command is a helper command that allows you to inspect the SQL Liquibase will run to revert the changeset specified in the rollbackOneChangeSet command. It is only available for Liquibase Pro users.

Uses

The rollbackOneChangeSetSQL command is typically used when you want inspect the raw SQL that Liquibase uses to revert your changeset when you run the rollbackOneChangeSet command, so that you don't unintentionally make a mistake.

Running the rollbackOneChangeSetSQL command

Before running the rollbackOneChangeSetSQL command, gather the following information from your DATABASECHANGELOG table or by running the history command:

  • The Author of the changeset you want to revert
  • The changeset ID of the changeset you want to revert
  • The file name (changeset path) of the changeset you want to revert

Then run the rollbackOneChangeSetSQL command, with your information:

                liquibase --changeLogFile=changelog.xml rollbackOneChangeSetSQL --changeSetAuthor="Liquibase Pro User" --changeSetId="1::createProc-proschema" --changeSetPath=changelog.xml --force
            

For more command specific help, type liquibase rollbackonechangesetSQL --help into the command prompt.

rollbackOneChangeSetSQL global parameters

Parameter Definition Requirement
--changeLogFile The root changelog Required
--url The JDBC database connection URL Required
--username The database username Required
--password The database password Required
--liquibaseProLicenseKey Your Liquibase Pro license key Required
--outputFile The path to the file where the Rollback SQL will be written Optional *

* If not specified, Rollback SQL output goes to STDOUT.

rollbackOneChangeSetSQL command parameters

Parameter Definition Requirement
--changesetId The changeset ID from the changelog. Required
--changesetAuthor The name of the author for the changeset. Required
--changesetPath The path to the changelog containing the changeset you want to roll back. Required
--rollbackScript The path to the script to use to perform the rollback. Optional **

** This option is only needed if the rollback is not already defined in the changelog, and if it is not a rollback that is automatically provided by Liquibase.

Output

When successful, the rollbackOneChangeSetSQL command produces the following output:

                
                    -- Lock Database  
UPDATE  databasechangeloglock  SET  LOCKED  =  TRUE,  LOCKEDBY  =  '2605:a601:ab18:0:205:1bff:feb1:45b2%eth1 (2605:a601:ab18:0:205:1bff:feb1:45b2%eth1)',  LOCKGRANTED  =  '2020-02-05 18:37:18.034'  WHERE  ID  =  1  AND  LOCKED  =  FALSE;  
-- *********************************************************************  
-- Rollback changeset 'postgres_lbpro_master_changelog.xml::4::functionForTrigger::Liquibase Pro User'  
-- *********************************************************************  
-- Change Log: postgres_lbpro_master_changelog.xml  
-- Ran at: 2/5/20 6:37 PM  
-- Against: intuser@jdbc:postgresql://localhost:5432/intuserdb?currentSchema=PROSCHEMA  
-- Liquibase version: 3.8.6  
-- *********************************************************************  
-- Rolling Back ChangeSet: postgres_lbpro_master_changelog.xml::4::functionForTrigger::Liquibase Pro User  
DELETE  FROM  "databasechangelog"  WHERE  ID  =  '4::functionForTrigger'  AND  AUTHOR  =  'Liquibase Pro User'  AND  FILENAME  =  'postgres_lbpro_master_changelog.xml';  
-- Release Database Lock  
UPDATE  databasechangeloglock  SET  LOCKED  =  FALSE,  LOCKEDBY  =  NULL,  LOCKGRANTED  =  NULL  WHERE  ID  =  1;
            

 

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