`update`

The update command deploys any changes that are in the changelog file and that have not been deployed to your database yet.

Uses

The update command is typically used to apply database changes that are specified in the changelog file to your database.

When you run the update command, Liquibase sequentially reads changesets in the changelog file, then it compares the unique identifiers of id, author, and path to filename to the values 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. However, if the status of the runOnChange or runAlways changeset attribute is set to TRUE, Liquibase will re-apply the changeset.

Syntax

To run the update command, specify the driver, classpath, and URL in the Liquibase properties file. For more information, see Create and Configure a liquibase.properties File. You can also specify these properties in your command line.

Then run the update command:

liquibase update --changelog-file=example-changelog.xml

Parameters

Global parameters

Attribute	Definition	Requirement
`--liquibase-catalog-name=<string>`	For MSSQL only: Specifies in what catalog the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional
`--liquibase-schema-name=<string>`	Specifies in what schema the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional

Command parameters

Attributes	Definition	Requirement
`--changelog-file=<string>`	The root changelog	Required
`--url=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`--change-exec-listener-class=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`--change-exec-listener-properties-file=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`--context-filter=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`--default-catalog-name=<string>`	Name of the default catalog to use for the database connection	Optional
`--default-schema-name=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Tip: In Liquibase v4.23.0+, camelCase for `defaultSchemaName` works successfully. If you are on an earlier version, camelCase may not work as expected. Note: The syntax `liquibase.command.defaultSchemaName` is valid for v4.19.0+. For prior versions, use `defaultSchemaName`.	Optional
`--driver=<string>`	The JDBC driver class	Optional
`--driver-properties-file=<string>`	The JDBC driver properties file	Optional
`--force-on-partial-changes=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`--label-filter=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`--password=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`--rollback-on-error=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`--show-summary=<string>`	Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. Default: `SUMMARY`. Available in Liquibase 4.24.0+. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`--show-summary-output=<string>`	Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL. Available in Liquibase 4.24.0+.	Optional
`--username=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Global parameters

Attribute	Definition	Requirement
`globalArgs: { liquibase-catalog-name: "<string>" }`	For MSSQL only: Specifies in what catalog the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional
`globalArgs: { liquibase-schema-name: "<string>" }`	Specifies in what schema the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional

Command parameters

Attributes	Definition	Requirement
`cmdArgs: { changelog-file: "<string>" }`	The root changelog	Required
`cmdArgs: { url: "<string>" }`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`cmdArgs: { change-exec-listener-class: "<string>" }`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`cmdArgs: { change-exec-listener-properties-file: "<string>" }`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`cmdArgs: { context-filter: "<string>" }`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`cmdArgs: { default-catalog-name: "<string>" }`	Name of the default catalog to use for the database connection	Optional
`cmdArgs: { default-schema-name: "<string>" }`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Tip: In Liquibase v4.23.0+, camelCase for `defaultSchemaName` works successfully. If you are on an earlier version, camelCase may not work as expected. Note: The syntax `liquibase.command.defaultSchemaName` is valid for v4.19.0+. For prior versions, use `defaultSchemaName`.	Optional
`cmdArgs: { driver: "<string>" }`	The JDBC driver class	Optional
`cmdArgs: { driver-properties-file: "<string>" }`	The JDBC driver properties file	Optional
`cmdArgs: { force-on-partial-changes: "<true\|false>" }`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`cmdArgs: { label-filter: "<string>" }`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`cmdArgs: { password: "<string>" }`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`cmdArgs: { rollback-on-error: "<true\|false>" }`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`cmdArgs: { show-summary: "<string>" }`	Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. Default: `SUMMARY`. Available in Liquibase 4.24.0+. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`cmdArgs: { show-summary-output: "<string>" }`	Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL. Available in Liquibase 4.24.0+.	Optional
`cmdArgs: { username: "<string>" }`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Global parameters

Attribute	Definition	Requirement
`liquibase.liquibaseCatalogName: <string>`	For MSSQL only: Specifies in what catalog the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional
`liquibase.liquibaseSchemaName: <string>`	Specifies in what schema the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional

Command parameters

Attributes	Definition	Requirement
`liquibase.command.changelogFile: <string>` `liquibase.command.<cmdName>.changelogFile: <string>`	The root changelog	Required
`liquibase.command.url: <string>` `liquibase.command.<cmdName>.url: <string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`liquibase.command.changeExecListenerClass: <string>` `liquibase.command.<cmdName>.changeExecListenerClass: <string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`liquibase.command.changeExecListenerPropertiesFile: <string>` `liquibase.command.<cmdName>.changeExecListenerPropertiesFile: <string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`liquibase.command.contextFilter: <string>` `liquibase.command.<cmdName>.contextFilter: <string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`liquibase.command.defaultCatalogName: <string>` `liquibase.command.<cmdName>.defaultCatalogName: <string>`	Name of the default catalog to use for the database connection	Optional
`liquibase.command.defaultSchemaName: <string>` `liquibase.command.<cmdName>.defaultSchemaName: <string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Tip: In Liquibase v4.23.0+, camelCase for `defaultSchemaName` works successfully. If you are on an earlier version, camelCase may not work as expected. Note: The syntax `liquibase.command.defaultSchemaName` is valid for v4.19.0+. For prior versions, use `defaultSchemaName`.	Optional
`liquibase.command.driver: <string>` `liquibase.command.<cmdName>.driver: <string>`	The JDBC driver class	Optional
`liquibase.command.driverPropertiesFile: <string>` `liquibase.command.<cmdName>.driverPropertiesFile: <string>`	The JDBC driver properties file	Optional
`liquibase.command.forceOnPartialChanges: <true\|false>` `liquibase.command.<cmdName>.forceOnPartialChanges: <true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`liquibase.command.labelFilter: <string>` `liquibase.command.<cmdName>.labelFilter: <string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`liquibase.command.password: <string>` `liquibase.command.<cmdName>.password: <string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`liquibase.command.rollbackOnError: <true\|false>` `liquibase.command.<cmdName>.rollbackOnError: <true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`liquibase.command.showSummary: <string>` `liquibase.command.<cmdName>.showSummary: <string>`	Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. Default: `SUMMARY`. Available in Liquibase 4.24.0+. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`liquibase.command.showSummaryOutput: <string>` `liquibase.command.<cmdName>.showSummaryOutput: <string>`	Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL. Available in Liquibase 4.24.0+.	Optional
`liquibase.command.username: <string>` `liquibase.command.<cmdName>.username: <string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Global parameters

Attribute	Definition	Requirement
`JAVA_OPTS=-Dliquibase.liquibaseCatalogName=<string>`	For MSSQL only: Specifies in what catalog the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional
`JAVA_OPTS=-Dliquibase.liquibaseSchemaName=<string>`	Specifies in what schema the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional

Command parameters

Attributes	Definition	Requirement
`JAVA_OPTS=-Dliquibase.command.changelogFile=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.changelogFile=<string>`	The root changelog	Required
`JAVA_OPTS=-Dliquibase.command.url=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.url=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`JAVA_OPTS=-Dliquibase.command.changeExecListenerClass=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.changeExecListenerClass=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`JAVA_OPTS=-Dliquibase.command.changeExecListenerPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.changeExecListenerPropertiesFile=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`JAVA_OPTS=-Dliquibase.command.contextFilter=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.contextFilter=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`JAVA_OPTS=-Dliquibase.command.defaultCatalogName=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.defaultCatalogName=<string>`	Name of the default catalog to use for the database connection	Optional
`JAVA_OPTS=-Dliquibase.command.defaultSchemaName=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.defaultSchemaName=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Tip: In Liquibase v4.23.0+, camelCase for `defaultSchemaName` works successfully. If you are on an earlier version, camelCase may not work as expected. Note: The syntax `liquibase.command.defaultSchemaName` is valid for v4.19.0+. For prior versions, use `defaultSchemaName`.	Optional
`JAVA_OPTS=-Dliquibase.command.driver=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.driver=<string>`	The JDBC driver class	Optional
`JAVA_OPTS=-Dliquibase.command.driverPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.driverPropertiesFile=<string>`	The JDBC driver properties file	Optional
`JAVA_OPTS=-Dliquibase.command.forceOnPartialChanges=<true\|false>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.forceOnPartialChanges=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`JAVA_OPTS=-Dliquibase.command.labelFilter=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.labelFilter=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`JAVA_OPTS=-Dliquibase.command.password=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.password=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`JAVA_OPTS=-Dliquibase.command.rollbackOnError=<true\|false>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.rollbackOnError=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`JAVA_OPTS=-Dliquibase.command.showSummary=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.showSummary=<string>`	Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. Default: `SUMMARY`. Available in Liquibase 4.24.0+. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`JAVA_OPTS=-Dliquibase.command.showSummaryOutput=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.showSummaryOutput=<string>`	Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL. Available in Liquibase 4.24.0+.	Optional
`JAVA_OPTS=-Dliquibase.command.username=<string>` `JAVA_OPTS=-Dliquibase.command.<cmdName>.username=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Global parameters

Attribute	Definition	Requirement
`LIQUIBASE_LIQUIBASE_CATALOG_NAME=<string>`	For MSSQL only: Specifies in what catalog the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional
`LIQUIBASE_LIQUIBASE_SCHEMA_NAME=<string>`	Specifies in what schema the Liquibase DATABASECHANGELOG and DATABASECHANGELOGLOCK tables will be managed	Optional

Command parameters

Attributes	Definition	Requirement
`LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_CHANGELOG_FILE=<string>`	The root changelog	Required
`LIQUIBASE_COMMAND_URL=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_URL=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`LIQUIBASE_COMMAND_CHANGE_EXEC_LISTENER_CLASS=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_CHANGE_EXEC_LISTENER_CLASS=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`LIQUIBASE_COMMAND_CHANGE_EXEC_LISTENER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_CHANGE_EXEC_LISTENER_PROPERTIES_FILE=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`LIQUIBASE_COMMAND_CONTEXT_FILTER=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_CONTEXT_FILTER=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`LIQUIBASE_COMMAND_DEFAULT_CATALOG_NAME=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_DEFAULT_CATALOG_NAME=<string>`	Name of the default catalog to use for the database connection	Optional
`LIQUIBASE_COMMAND_DEFAULT_SCHEMA_NAME=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_DEFAULT_SCHEMA_NAME=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Tip: In Liquibase v4.23.0+, camelCase for `defaultSchemaName` works successfully. If you are on an earlier version, camelCase may not work as expected. Note: The syntax `liquibase.command.defaultSchemaName` is valid for v4.19.0+. For prior versions, use `defaultSchemaName`.	Optional
`LIQUIBASE_COMMAND_DRIVER=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_DRIVER=<string>`	The JDBC driver class	Optional
`LIQUIBASE_COMMAND_DRIVER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_DRIVER_PROPERTIES_FILE=<string>`	The JDBC driver properties file	Optional
`LIQUIBASE_COMMAND_FORCE_ON_PARTIAL_CHANGES=<true\|false>` `LIQUIBASE_COMMAND_<CMDNAME>_FORCE_ON_PARTIAL_CHANGES=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`LIQUIBASE_COMMAND_LABEL_FILTER=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_LABEL_FILTER=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`LIQUIBASE_COMMAND_PASSWORD=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_PASSWORD=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`LIQUIBASE_COMMAND_ROLLBACK_ON_ERROR=<true\|false>` `LIQUIBASE_COMMAND_<CMDNAME>_ROLLBACK_ON_ERROR=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`LIQUIBASE_COMMAND_SHOW_SUMMARY=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_SHOW_SUMMARY=<string>`	Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. Default: `SUMMARY`. Available in Liquibase 4.24.0+. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`LIQUIBASE_COMMAND_SHOW_SUMMARY_OUTPUT=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_SHOW_SUMMARY_OUTPUT=<string>`	Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL. Available in Liquibase 4.24.0+.	Optional
`LIQUIBASE_COMMAND_USERNAME=<string>` `LIQUIBASE_COMMAND_<CMDNAME>_USERNAME=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Note: The username and password attributes are not required for connections and systems which use alternate means of authentication. Also, you can specify database credentials as part of the url attribute.

Output

Liquibase Version: 4.9.1
Liquibase Community 4.9.1 by Liquibase
Running Changeset: example-changelog.sql::1::your.name
Running Changeset: example-changelog.sql::2::your.name
Running Changeset: example-changelog.sql::3::other.dev

Liquibase command 'update' was executed successfully.

update

Uses

Syntax

Parameters

Global parameters

Command parameters

Global parameters

Command parameters

Global parameters

Command parameters

Global parameters

Command parameters

Global parameters

Command parameters

Related links

`update`