9.12.43 update-to-tag
Syntax
Liquibase|lb update-to-tag|uptt OPTIONSThe update-to-tag command will deploy changes only 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 command. An update-to-tag-sql
should always be run to review the SQL before running update-to-tag.
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 Debug logging is |
- |
-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. |
- |
-show-summary|-shs
<show-summary> {OFF|SUMMARY|VERBOSE}
|
Produces a summary list of any changesets skipped and why they were skipped. Valid values are OFF, SUMMARY, and VERBOSE. | SUMMARY |
-output-default-schema|-ouds |
Controls whether names of objects in the default schema are fully qualified or not. If false, only objects outside the default schema are fully qualified. | False |
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 versions
-- Execute an update-to-tag using a tag specified in tagDatabase in the changelog file
SQL> lb update-to-tag -tag version1 -changelog-file controller.xml