9.12.42 update-testing-rollback

Updates database, then rolls back changes before updating again. It provides testing of rollback funtionality.

Syntax

Liquibase|lb update-testing-rollback|uptr {OPTIONS}

Use only when all pending changelogs have been verified as ready to be deployed.

A multi-step operation is used and runs in sequential order:
update changeset1; update changeset2; update changeset3\
rollback changeset3; rollback changeset2; rollback changeset1
update changeset1; update changeset2; update changeset3

Options

Option Description Default
Required
-changelog-file|-chf The root changelog file. -
Optional
-contexts|-co Context string to use for filtering which changes to operate on. -
-database-changelog-table-name|-dactn Name of table to use for tracking change history. -
-debug|-de Enable debug output. -
-default-schema-name|-desn The default schema name to use for the database connection. -
-defaults-file|-def Fully qualified path to the properties file you want to use. Example: -defaults-file/tmp/liquibase.properties -
-labels|-la Label expression to use for filtering the changes to operate on. -
-liquibase-schema-name|-lbsn Schema to use for Liquibase objects. -
-liquibase-tablespace-name|-lbtn Tablespace to use for Liquibase objects. -
-log|-lo

Enable logging.

Standard logging is INFO level (no debug flag).

Debug logging is FINEST level (both log and debug flag).

-
-output-default-schema|-ouds Control whether names of objects in the default schema are fully qualified or not. If true they are qualified. If false, only objects outside the default schema are fully qualified. False
-output-file|-ouf The name of the file to write the output to. -
-overwrite-files|-ovf Overwrite any existing files in the directory. This will not affect other files. -
-search-path|-sep

Complete list of locations to search for files such as changelog files.

You can specify multiple paths by separating them with commas.

-
-secure-parsing|-scp

If true, remove functionality from file parsers that could be used insecurely.

An example is disabling remote XML entity support.

-