history

The history command lists all deployed changesets and their deploymentIds. The history command does not modify the database.

Uses

The history command is typically used when you want to inspect a particular group of changes to ensure that they have been applied to the database. It shows a list of deployment IDs, the date each deployment was made (using the timezone of the machine the command was run on), the changeset path, ID, and author, and any associated tags. This information is pulled from the DATABASECHANGELOGHISTORY table. You can display this information as text or in a table.

Syntax

To run the history 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 history command:

liquibase history

Parameters

Global parameters

Attribute Definition Requirement

--output-file=<string>

File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.

 Optional

Command parameters

Attribute Definition Requirement

--url=<string>

The JDBC database connection URL. See Using JDBC URL in Liquibase.

 Required

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

Note: In the properties file and JAVA_OPTS only: in 4.18.0 and earlier, specify this parameter using the syntax defaultSchemaName. In 4.19.0 and later, use the syntax liquibase.command.defaultSchemaName.

Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set --preserve-schema-case to true. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a DatabaseException error if you specify a mixed-case value of defaultSchemaName. In 4.23.0 and later, the Liquibase validator accepts any casing.

 Optional

--driver=<string>

The JDBC driver class

 Optional

--driver-properties-file=<string>

The JDBC driver properties file

 Optional

--format=<string>

Specifies the format of the output. TEXT displays the output as plain text. TABULAR groups changesets by deployment ID and displays other information (timestamp, path, author, ID, and checksum) in individual table cells. Default: TABULAR.

 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

--show-tags=<true|false>

Liquibase 4.31.0+. If true, Liquibase only shows tagged changeset in the command output. An alternative to looking for tag information in the DATABASECHANGELOG table. If false, Liquibase shows all changesets. Default: false.

 Optional

--tag-filter=<string>

Liquibase 4.31.0+. Filter tags to show in the command output. Only changesets associated with the tags you specify will be shown. Separate multiple values with commas.

 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: { output-file: "<string>" }

File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.

 Optional

Command parameters

Attribute Definition Requirement

cmdArgs: { url: "<string>" }

The JDBC database connection URL. See Using JDBC URL in Liquibase.

 Required

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.

Note: In the properties file and JAVA_OPTS only: in 4.18.0 and earlier, specify this parameter using the syntax defaultSchemaName. In 4.19.0 and later, use the syntax liquibase.command.defaultSchemaName.

Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set --preserve-schema-case to true. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a DatabaseException error if you specify a mixed-case value of defaultSchemaName. In 4.23.0 and later, the Liquibase validator accepts any casing.

 Optional

cmdArgs: { driver: "<string>" }

The JDBC driver class

 Optional

cmdArgs: { driver-properties-file: "<string>" }

The JDBC driver properties file

 Optional

cmdArgs: { format: "<string>" }

Specifies the format of the output. TEXT displays the output as plain text. TABULAR groups changesets by deployment ID and displays other information (timestamp, path, author, ID, and checksum) in individual table cells. Default: TABULAR.

 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: { show-tags: "<true|false>" }

Liquibase 4.31.0+. If true, Liquibase only shows tagged changeset in the command output. An alternative to looking for tag information in the DATABASECHANGELOG table. If false, Liquibase shows all changesets. Default: false.

 Optional

cmdArgs: { tag-filter: "<string>" }

Liquibase 4.31.0+. Filter tags to show in the command output. Only changesets associated with the tags you specify will be shown. Separate multiple values with commas.

 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.outputFile: <string>

File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.

 Optional

Command parameters

Attribute Definition Requirement

liquibase.command.url: <string>

liquibase.command.history.url: <string>

The JDBC database connection URL. See Using JDBC URL in Liquibase.

 Required

liquibase.command.defaultCatalogName: <string>

liquibase.command.history.defaultCatalogName: <string>

Name of the default catalog to use for the database connection

 Optional

liquibase.command.defaultSchemaName: <string>

liquibase.command.history.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.

Note: In the properties file and JAVA_OPTS only: in 4.18.0 and earlier, specify this parameter using the syntax defaultSchemaName. In 4.19.0 and later, use the syntax liquibase.command.defaultSchemaName.

Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set --preserve-schema-case to true. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a DatabaseException error if you specify a mixed-case value of defaultSchemaName. In 4.23.0 and later, the Liquibase validator accepts any casing.

 Optional

liquibase.command.driver: <string>

liquibase.command.history.driver: <string>

The JDBC driver class

 Optional

liquibase.command.driverPropertiesFile: <string>

liquibase.command.history.driverPropertiesFile: <string>

The JDBC driver properties file

 Optional

liquibase.command.format: <string>

liquibase.command.history.format: <string>

Specifies the format of the output. TEXT displays the output as plain text. TABULAR groups changesets by deployment ID and displays other information (timestamp, path, author, ID, and checksum) in individual table cells. Default: TABULAR.

 Optional

liquibase.command.password: <string>

liquibase.command.history.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.showTags: <true|false>

liquibase.command.history.showTags: <true|false>

Liquibase 4.31.0+. If true, Liquibase only shows tagged changeset in the command output. An alternative to looking for tag information in the DATABASECHANGELOG table. If false, Liquibase shows all changesets. Default: false.

 Optional

liquibase.command.tagFilter: <string>

liquibase.command.history.tagFilter: <string>

Liquibase 4.31.0+. Filter tags to show in the command output. Only changesets associated with the tags you specify will be shown. Separate multiple values with commas.

 Optional

liquibase.command.username: <string>

liquibase.command.history.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.outputFile=<string>

File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.

 Optional

Command parameters

Attribute Definition Requirement

JAVA_OPTS=-Dliquibase.command.url=<string>

JAVA_OPTS=-Dliquibase.command.history.url=<string>

The JDBC database connection URL. See Using JDBC URL in Liquibase.

 Required

JAVA_OPTS=-Dliquibase.command.defaultCatalogName=<string>

JAVA_OPTS=-Dliquibase.command.history.defaultCatalogName=<string>

Name of the default catalog to use for the database connection

 Optional

JAVA_OPTS=-Dliquibase.command.defaultSchemaName=<string>

JAVA_OPTS=-Dliquibase.command.history.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.

Note: In the properties file and JAVA_OPTS only: in 4.18.0 and earlier, specify this parameter using the syntax defaultSchemaName. In 4.19.0 and later, use the syntax liquibase.command.defaultSchemaName.

Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set --preserve-schema-case to true. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a DatabaseException error if you specify a mixed-case value of defaultSchemaName. In 4.23.0 and later, the Liquibase validator accepts any casing.

 Optional

JAVA_OPTS=-Dliquibase.command.driver=<string>

JAVA_OPTS=-Dliquibase.command.history.driver=<string>

The JDBC driver class

 Optional

JAVA_OPTS=-Dliquibase.command.driverPropertiesFile=<string>

JAVA_OPTS=-Dliquibase.command.history.driverPropertiesFile=<string>

The JDBC driver properties file

 Optional

JAVA_OPTS=-Dliquibase.command.format=<string>

JAVA_OPTS=-Dliquibase.command.history.format=<string>

Specifies the format of the output. TEXT displays the output as plain text. TABULAR groups changesets by deployment ID and displays other information (timestamp, path, author, ID, and checksum) in individual table cells. Default: TABULAR.

 Optional

JAVA_OPTS=-Dliquibase.command.password=<string>

JAVA_OPTS=-Dliquibase.command.history.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.showTags=<true|false>

JAVA_OPTS=-Dliquibase.command.history.showTags=<true|false>

Liquibase 4.31.0+. If true, Liquibase only shows tagged changeset in the command output. An alternative to looking for tag information in the DATABASECHANGELOG table. If false, Liquibase shows all changesets. Default: false.

 Optional

JAVA_OPTS=-Dliquibase.command.tagFilter=<string>

JAVA_OPTS=-Dliquibase.command.history.tagFilter=<string>

Liquibase 4.31.0+. Filter tags to show in the command output. Only changesets associated with the tags you specify will be shown. Separate multiple values with commas.

 Optional

JAVA_OPTS=-Dliquibase.command.username=<string>

JAVA_OPTS=-Dliquibase.command.history.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_OUTPUT_FILE=<string>

File path to where the command output will be written. If not specified, output goes to STDOUT. See --output-file.

 Optional

Command parameters

Attribute Definition Requirement

LIQUIBASE_COMMAND_URL=<string>

LIQUIBASE_COMMAND_HISTORY_URL=<string>

The JDBC database connection URL. See Using JDBC URL in Liquibase.

 Required

LIQUIBASE_COMMAND_DEFAULT_CATALOG_NAME=<string>

LIQUIBASE_COMMAND_HISTORY_DEFAULT_CATALOG_NAME=<string>

Name of the default catalog to use for the database connection

 Optional

LIQUIBASE_COMMAND_DEFAULT_SCHEMA_NAME=<string>

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

Note: In the properties file and JAVA_OPTS only: in 4.18.0 and earlier, specify this parameter using the syntax defaultSchemaName. In 4.19.0 and later, use the syntax liquibase.command.defaultSchemaName.

Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set --preserve-schema-case to true. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a DatabaseException error if you specify a mixed-case value of defaultSchemaName. In 4.23.0 and later, the Liquibase validator accepts any casing.

 Optional

LIQUIBASE_COMMAND_DRIVER=<string>

LIQUIBASE_COMMAND_HISTORY_DRIVER=<string>

The JDBC driver class

 Optional

LIQUIBASE_COMMAND_DRIVER_PROPERTIES_FILE=<string>

LIQUIBASE_COMMAND_HISTORY_DRIVER_PROPERTIES_FILE=<string>

The JDBC driver properties file

 Optional

LIQUIBASE_COMMAND_FORMAT=<string>

LIQUIBASE_COMMAND_HISTORY_FORMAT=<string>

Specifies the format of the output. TEXT displays the output as plain text. TABULAR groups changesets by deployment ID and displays other information (timestamp, path, author, ID, and checksum) in individual table cells. Default: TABULAR.

 Optional

LIQUIBASE_COMMAND_PASSWORD=<string>

LIQUIBASE_COMMAND_HISTORY_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_SHOW_TAGS=<true|false>

LIQUIBASE_COMMAND_HISTORY_SHOW_TAGS=<true|false>

Liquibase 4.31.0+. If true, Liquibase only shows tagged changeset in the command output. An alternative to looking for tag information in the DATABASECHANGELOG table. If false, Liquibase shows all changesets. Default: false.

 Optional

LIQUIBASE_COMMAND_TAG_FILTER=<string>

LIQUIBASE_COMMAND_HISTORY_TAG_FILTER=<string>

Liquibase 4.31.0+. Filter tags to show in the command output. Only changesets associated with the tags you specify will be shown. Separate multiple values with commas.

 Optional

LIQUIBASE_COMMAND_USERNAME=<string>

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

When successful, the history command produces the following output:

Liquibase Version: 4.24.0
Liquibase Open Source 4.24.0 by Liquibase
Liquibase History for jdbc:h2:tcp://localhost:9090/mem:dev

+---------------+--------------------+-----------------------+------------------+--------------+-----+
| Deployment ID | Update Date        | Changelog Path        | Changeset Author | Changeset ID | Tag |
+---------------+--------------------+-----------------------+------------------+--------------+-----+
| 8688194246    | 10/30/23, 11:49 AM | db/changelog/changelog.xml | fbiville       | merge-duplicated-person-nodes           |     |
+---------------+--------------------+-----------------------+------------------+--------------+-----+
| 8688194246    | 10/30/23, 11:49 AM | db/changelog/changelog.xml | fbiville       | remove-duplicate-relationships            |     |
+---------------+--------------------+-----------------------+------------------+--------------+-----+
| 8688194246    | 10/30/23, 11:49 AM | db/changelog/changelog.xml | mgazanayi      | index-person             |     |
+---------------+--------------------+-----------------------+------------------+--------------+-----+

Liquibase command 'history' was executed successfully.

If you specify history --format=TEXT, the command produces the following output:

Liquibase Version: 4.24.0
Liquibase Community 4.24.0 by Liquibase
Liquibase History for jdbc:h2:tcp://localhost:9090/mem:dev

- Database updated at 11/2/23, 10:19 AM. Applied 3 changeset(s) in 0.027s, DeploymentId: 8941967528
example-changelog.sql::1::your.name
example-changelog.sql::2::your.name
example-changelog.sql::3::other.dev

Liquibase command 'history' was executed successfully.

Related links