update-to-tag-sql

9.12.44 update-to-tag-sql

Generate the SQL from the newest changeset up to and including the changeset with the specified tag.

Syntax

Liquibase|lb update-to-tag-sql|uptts {OPTIONS}

An update-to-tag-sql should always be run to review the SQL before running update-to-tag The update-to-tag-sql command will generate SQL when you have previously added a tag Database Change Type in your changelog file. You cannot use the update-to-tag command with the reference to a tag created in the DATABASECHANGELOG table using the tag cde command.

Options

Option	Description	Default
Required
`-changelog-file\|-chf`	The root changelog file.	-
`-tag\|-ta`	The tag to use during the execution of the command.	-
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.	True

Example

Update database with the changesets up to and including the changeset with the specified database tag.

SQL> cd <lb-changes-directory>
-- Edit changelog file and add tagDatabase entries for version1
SQL> lb update-to-tag-sql -tag version1 -changelog-file controller.xml