9.12.38 update
Syntax
Liquibase|lb update|up {OPTIONS}When you run the update command, the changesets in the changelog file
are read sequentially. The unique identifiers (file::id::author) in the file are
compared to those stored in the DATABASECHANGELOG table.
- If the unique identifiers do not exist, Liquibase will apply the changeset to the database.
-
If the unique identifiers exist, the MD5Sum of the changeset is compared to the one in the database.
If they are different, Liquibase will produce an error message that someone has changed it unexpectedly.
If the status of the runOnChange or runAlways changeset attribute is set to TRUE, Liquibase will re-apply the changeset. Example: <changeSet id="2" author="bob" runAlways="true">
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 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. |
True |
-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 |
-override-app-alias|-ovaa |
Override value to be used for the APEX application alias. | - |
-override-app-id|-ovai |
Override value to be used for the APEX application id. | - |
-override-app-schema|-ovas |
Override value to be used for the APEX workspace schema. | - |
-override-app-workspace|-ovaw |
Override value to be used for the APEX application workspace. | - |