9.12.25 mark-next-changeset-ran-sql
Writes the SQL used to mark the next change you apply as executed in your
database.
Syntax
Liquibase|lb mark-next-changeset-ran-sql|mancrs {OPTIONS}Options
| Option | Description | Default |
|---|---|---|
| Required | ||
-changelog-file|-chf |
The root changelog file. | - |
| 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 |
- |
-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 |
-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. |
- |
-output-file|-ouf |
The name of the file to write the output to. | - |