9.12.35 tag
Syntax
Liquibase|lb tag|ta {OPTIONS}
For example, you can use the tag to mark the current database state for version,
release, and so on. The tag is added to the last row in the
DATABASECHANGELOG
table.
Options
Option | Description | Default |
---|---|---|
Required | ||
-tag|-ta |
The tag to use during the execution of the command. | - |
Optional | ||
-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 |
- |
-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 |
-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
Create initial tag and version tags.
-- Set default output path
SQL> cd <output-files-path>
-- Connect to target and add base tag
SQL> connect <db-connect-string>
SQL> lb tag -tag baseversion1
-- Apply update for version adding and add new tag for each version
SQL> lb update -changelog-file controller.xml
SQL> lb tag -tag version1