unexpected-changesets

9.12.37 unexpected-changesets

Generate a list of changesets that have been executed but are not in the current changelog.

Syntax

Liquibase|lb unexpected-changesets|unc {OPTIONS}

This command detects and compares the changes between the DATABASECHANGELOG table and the current changelog and reports:

Changesets in the DATABASECHANGELOG table that do not exist in the current changelog.
Previously deployed changesets that were deleted from your current changelog.

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 <defaults-file> {FILE}`	Fully qualified path to the properties file you want to use. For 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, which can be used insecurely. An example is disabling remote XML entity support.	True
`-verbose \|-ve`	Verbose flag	True

Example

Report unexpected changesets.

-- Set default output path
SQL> cd <output-files-path>
-- Connect to target and run command
SQL> connect <db-connect-string>
SQL> lb unexpected-changesets -changelog-file controller.xml