9.12.39 update-count

Deploy the specified number of changes from the changelog file.

Syntax

Liquibase|lb update-count|upc {OPTIONS}

The update-count command applies changes and updates changesets sequentially, starting from the top of the changelog file until the number specified is reached.

  • 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. -
-count|-cu The number of changes to apply. -
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|l- 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 INFO level (no debug flag).

Debug logging is FINEST level (both log and debug flag).

-
-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

Example

Update database with the specified number of changesets in the changelog file.

SQL> cd <lb-changes-directory>
SQL> lb update -changelog-file controller.xml -count 2