9.12.7 data

Generate changelogs for the data. Creates a changelog for data from all objects or as filters are specified.

Syntax

Liquibase|lb data|da {OPTIONS}

Options

Option Description Default
-data-output-directory|-daod <data-output-directory> Directory to write data to, only applicable when <DIFF_TYPE> includes data. -
-database-changelog-table-name|-dactn <database-changelog-table-name> Name of table to use for tracking change history. -
-debug|-de Enable debug output. -
-default-schema-name|-desn <default-schema-name> The default schema name to use for the database connection. -
-defaults-file|-def <defaults-file> {FILE} Fully qualified path to the properties file you want to use. Example: -defaults-file/tmp/liquibase.properties -
-exclude-objects|-exo <exclude-objects> Objects to exclude from diff. -
-include-objects|-ino <include-objects> Objects to include in diff. -
-include-schema|-ins <include-schema> If true, the schema is included in generated changesets. False
-include-tablespace|-int <include-tablespace> Include the tablespace attribute in the changelog. False
-liquibase-schema-name|-lbsn <liquibase-schema-name> Schema to use for Liquibase objects. -
-liquibase-tablespace-name|-lbtn <liquibase-tablespace-name> 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 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
-output-file|-ouf <output-file> The name of the file to write the output to. -
-overwrite-files|-ovf Overwrite any existing files in directory. This will not affect other files. -
-schemas|-sc <schemas> Schemas to include operation. -
-search-path|-sep <search-path> Complete list of locations to search for files such as changelog files. Multiple paths can be specified by separating them with commas. -
-secure-parsing|-scp <secure-parsing> Keep functionality from file parsers which could be used insecurely. Examples include (but not limited to) disabling remote XML entity support. True