dbcl-history

Note: This is a Liquibase Pro feature, so you need a Liquibase Pro License Key to use it.

dbcl-history is a command that displays the DATABASECHANGELOGHISTORY table. By default, the command displays the table in STDOUT. It is available in Liquibase 4.27.0 and later. It is only available to Liquibase Pro users.

Uses

The DATABASECHANGELOGHISTORY (DBCLH) table contains all changes ever made to your database with Liquibase, including rollbacks and other changes not included in the DATABASECHANGELOG table (DBCL). You can see the DBCLH table in your database by running a SQL query:

SELECT * FROM DATABASECHANGELOGHISTORY;

However, you may also want Liquibase to display the DBCLH in your command line or an output file without running a SQL query. You may also want to display it in a machine-readable format. The dbcl-history command lets you do all these things. If you have Structured Logging enabled, Liquibase also sends the output of dbcl-history to structured logs. This lets you automatically feed your data into third-party logging tools.

Easily accessing the DBCLH table enables you to identify patterns in your deployments that later have to be rolled back. By understanding these patterns, you can avoid these problems and speed up your development cycle.

Syntax

To display the DBCLH table in STDOUT, run the dbcl-history command in your command line or in a flow file. For example, to generate human-readable JSON output:

liquibase dbcl-history --format=JSON_PRETTY --verbose
stages:
  Default:
    actions:
      - type: liquibase
        command: dbcl-history
        cmdArgs: {format: JSON_PRETTY, verbose}

You can use the --output-file global parameter to send command output to a file instead of the console:

liquibase --output-file=dbclh_2024-03-15.json dbcl-history --format=JSON_PRETTY --verbose

Parameters

Global parameters

Parameter Definition Requirement

--license-key=<string>

Your Liquibase Pro license key

 Required

--dbclhistory-capture-extensions=<true|false>

If true, installed extensions are captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-extensions.

 Optional

--dbclhistory-capture-sql=<true|false>

If true, SQL generated by commands is captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-sql.

 Optional

--dbclhistory-enabled=<true|false>

Enables the DATABASECHANGELOGHISTORY table. This table includes records of rollbacks, dropAlls, and repeated runOnChange type activity, which is not available in the standard DATABASECHANGELOG table. Liquibase 4.27.0+. Default: false. See --dbclhistory-enabled.

 Optional

--dbclhistory-severity=<string>

The exit code for Liquibase to return if an exception is encountered while recording events to the DATABASECHANGELOGHISTORY table. Valid values are INFO (0), MINOR (1), MAJOR (2), CRITICAL (3), and BLOCKER (4), from least severe to most severe. Liquibase 4.27.0+. Default: 1. See --dbclhistory-severity.

 Optional

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

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

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

--format=<string>

Specifies the format of the output. Valid values are JSON and JSON_PRETTY. Specifying JSON formats the output as machine-readable JSON without indentation or line breaks. Specifying JSON_PRETTY adds whitespace to be human-readable. Default: JSON.

 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

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

--verbose=<true|false>

Specifies the detail level of the command's output. Default: false.

 Optional

Global parameters

Parameter Definition Requirement

globalArgs: { license-key: "<string>" }

Your Liquibase Pro license key

 Required

cmdArgs: { dbclhistory-capture-extensions: "<true|false>" }

If true, installed extensions are captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-extensions.

 Optional

cmdArgs: { dbclhistory-capture-sql: "<true|false>" }

If true, SQL generated by commands is captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-sql.

 Optional

cmdArgs: { dbclhistory-enabled: "<true|false>" }

Enables the DATABASECHANGELOGHISTORY table. This table includes records of rollbacks, dropAlls, and repeated runOnChange type activity, which is not available in the standard DATABASECHANGELOG table. Liquibase 4.27.0+. Default: false. See --dbclhistory-enabled.

 Optional

cmdArgs: { dbclhistory-severity: "<string>" }

The exit code for Liquibase to return if an exception is encountered while recording events to the DATABASECHANGELOGHISTORY table. Valid values are INFO (0), MINOR (1), MAJOR (2), CRITICAL (3), and BLOCKER (4), from least severe to most severe. Liquibase 4.27.0+. Default: 1. See --dbclhistory-severity.

 Optional

cmdArgs: { 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

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

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

Specifies the format of the output. Valid values are JSON and JSON_PRETTY. Specifying JSON formats the output as machine-readable JSON without indentation or line breaks. Specifying JSON_PRETTY adds whitespace to be human-readable. Default: JSON.

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

cmdArgs: { verbose: "<true|false>" }

Specifies the detail level of the command's output. Default: false.

 Optional

Global parameters

Parameter Definition Requirement

liquibase.licenseKey: <string>

Your Liquibase Pro license key

 Required

liquibase.command.dbclhistory.captureExtensions: <true|false>

liquibase.command.<cmdName>.dbclhistory.captureExtensions: <true|false>

If true, installed extensions are captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-extensions.

 Optional

liquibase.command.dbclhistory.captureSql: <true|false>

liquibase.command.<cmdName>.dbclhistory.captureSql: <true|false>

If true, SQL generated by commands is captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-sql.

 Optional

liquibase.command.dbclhistory.enabled: <true|false>

liquibase.command.<cmdName>.dbclhistory.enabled: <true|false>

Enables the DATABASECHANGELOGHISTORY table. This table includes records of rollbacks, dropAlls, and repeated runOnChange type activity, which is not available in the standard DATABASECHANGELOG table. Liquibase 4.27.0+. Default: false. See --dbclhistory-enabled.

 Optional

liquibase.command.dbclhistory.severity: <string>

liquibase.command.<cmdName>.dbclhistory.severity: <string>

The exit code for Liquibase to return if an exception is encountered while recording events to the DATABASECHANGELOGHISTORY table. Valid values are INFO (0), MINOR (1), MAJOR (2), CRITICAL (3), and BLOCKER (4), from least severe to most severe. Liquibase 4.27.0+. Default: 1. See --dbclhistory-severity.

 Optional

liquibase.command.outputFile: <string>

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

Parameter Definition Requirement

liquibase.command.url: <string>

liquibase.command.<cmdName>.url: <string>

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

 Required

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

liquibase.command.<cmdName>.format: <string>

Specifies the format of the output. Valid values are JSON and JSON_PRETTY. Specifying JSON formats the output as machine-readable JSON without indentation or line breaks. Specifying JSON_PRETTY adds whitespace to be human-readable. Default: JSON.

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

liquibase.command.verbose: <true|false>

liquibase.command.<cmdName>.verbose: <true|false>

Specifies the detail level of the command's output. Default: false.

 Optional

Global parameters

Parameter Definition Requirement

JAVA_OPTS=-Dliquibase.licenseKey=<string>

Your Liquibase Pro license key

 Required

JAVA_OPTS=-Dliquibase.command.dbclhistory.captureExtensions=<true|false>

JAVA_OPTS=-Dliquibase.command.<cmdName>.dbclhistory.captureExtensions=<true|false>

If true, installed extensions are captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-extensions.

 Optional

JAVA_OPTS=-Dliquibase.command.dbclhistory.captureSql=<true|false>

JAVA_OPTS=-Dliquibase.command.<cmdName>.dbclhistory.captureSql=<true|false>

If true, SQL generated by commands is captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-sql.

 Optional

JAVA_OPTS=-Dliquibase.command.dbclhistory.enabled=<true|false>

JAVA_OPTS=-Dliquibase.command.<cmdName>.dbclhistory.enabled=<true|false>

Enables the DATABASECHANGELOGHISTORY table. This table includes records of rollbacks, dropAlls, and repeated runOnChange type activity, which is not available in the standard DATABASECHANGELOG table. Liquibase 4.27.0+. Default: false. See --dbclhistory-enabled.

 Optional

JAVA_OPTS=-Dliquibase.command.dbclhistory.severity=<string>

JAVA_OPTS=-Dliquibase.command.<cmdName>.dbclhistory.severity=<string>

The exit code for Liquibase to return if an exception is encountered while recording events to the DATABASECHANGELOGHISTORY table. Valid values are INFO (0), MINOR (1), MAJOR (2), CRITICAL (3), and BLOCKER (4), from least severe to most severe. Liquibase 4.27.0+. Default: 1. See --dbclhistory-severity.

 Optional

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

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

Parameter Definition Requirement

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.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.format=<string>

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

Specifies the format of the output. Valid values are JSON and JSON_PRETTY. Specifying JSON formats the output as machine-readable JSON without indentation or line breaks. Specifying JSON_PRETTY adds whitespace to be human-readable. Default: JSON.

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

JAVA_OPTS=-Dliquibase.command.verbose=<true|false>

JAVA_OPTS=-Dliquibase.command.<cmdName>.verbose=<true|false>

Specifies the detail level of the command's output. Default: false.

 Optional

Global parameters

Parameter Definition Requirement

LIQUIBASE_LICENSE_KEY=<string>

Your Liquibase Pro license key

 Required

LIQUIBASE_COMMAND_DBCLHISTORY_CAPTURE_EXTENSIONS=<true|false>

LIQUIBASE_COMMAND_<CMDNAME>_DBCLHISTORY_CAPTURE_EXTENSIONS=<true|false>

If true, installed extensions are captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-extensions.

 Optional

LIQUIBASE_COMMAND_DBCLHISTORY_CAPTURE_SQL=<true|false>

LIQUIBASE_COMMAND_<CMDNAME>_DBCLHISTORY_CAPTURE_SQL=<true|false>

If true, SQL generated by commands is captured in the DATABASECHANGELOGHISTORY table. Liquibase 4.27.0+. Default: true. See --dbclhistory-capture-sql.

 Optional

LIQUIBASE_COMMAND_DBCLHISTORY_ENABLED=<true|false>

LIQUIBASE_COMMAND_<CMDNAME>_DBCLHISTORY_ENABLED=<true|false>

Enables the DATABASECHANGELOGHISTORY table. This table includes records of rollbacks, dropAlls, and repeated runOnChange type activity, which is not available in the standard DATABASECHANGELOG table. Liquibase 4.27.0+. Default: false. See --dbclhistory-enabled.

 Optional

LIQUIBASE_COMMAND_DBCLHISTORY_SEVERITY=<string>

LIQUIBASE_COMMAND_<CMDNAME>_DBCLHISTORY_SEVERITY=<string>

The exit code for Liquibase to return if an exception is encountered while recording events to the DATABASECHANGELOGHISTORY table. Valid values are INFO (0), MINOR (1), MAJOR (2), CRITICAL (3), and BLOCKER (4), from least severe to most severe. Liquibase 4.27.0+. Default: 1. See --dbclhistory-severity.

 Optional

LIQUIBASE_COMMAND_OUTPUT_FILE=<string>

LIQUIBASE_COMMAND_<CMDNAME>_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

Parameter Definition Requirement

LIQUIBASE_COMMAND_URL=<string>

LIQUIBASE_COMMAND_<CMDNAME>_URL=<string>

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

 Required

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_FORMAT=<string>

LIQUIBASE_COMMAND_<CMDNAME>_FORMAT=<string>

Specifies the format of the output. Valid values are JSON and JSON_PRETTY. Specifying JSON formats the output as machine-readable JSON without indentation or line breaks. Specifying JSON_PRETTY adds whitespace to be human-readable. Default: JSON.

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

LIQUIBASE_COMMAND_VERBOSE=<true|false>

LIQUIBASE_COMMAND_<CMDNAME>_VERBOSE=<true|false>

Specifies the detail level of the command's output. Default: false.

 Optional

Output

[{"arguments":"--dbclhistory-enabled=true --license-key ***** update","author":"your.name","command":"update","comments":"example-comment","contexts":"example-context","deploymentId":"5441340119","description":"createTable tableName=person","end":"2024-01-16 16:42:20.158","executedSql":"CREATE TABLE PUBLIC.person (id INT GENERATED BY DEFAULT AS IDENTITY NOT NULL, name VARCHAR(50) NOT NULL, address1 VARCHAR(50), address2 VARCHAR(50), city VARCHAR(30), CONSTRAINT PK_PERSON PRIMARY KEY (id));","extensions":"internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal...","filename":"example-changelog.xml","hostname":"LAPTOP-74GFS93J","id":"1","internalCommand":"update","labels":"example-label","liquibaseInterface":"cli","liquibaseVersion":"DEV","md5Sum":"9:884ea70a8e61427b7b1a217a62954c48","outcome":"success","start":"2024-01-16 16:42:20.144","systemUser":"liquibase-user","tag":"null"},{"arguments":"--dbclhistory-enabled=true --license-key ***** update","author":"your.name","command":"update","comments":"example-comment","contexts":"example-context","deploymentId":"5441340119","description":"createTable tableName=company","end":"2024-01-16 16:42:20.216","executedSql":"CREATE TABLE PUBLIC.company (id INT GENERATED BY DEFAULT AS IDENTITY NOT NULL, name VARCHAR(50) NOT NULL, address1 VARCHAR(50), address2 VARCHAR(50), city VARCHAR(30), CONSTRAINT PK_COMPANY PRIMARY KEY (id));","extensions":"internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal...","filename":"example-changelog.xml","hostname":"LAPTOP-74GFS93J","id":"2","internalCommand":"update","labels":"example-label","liquibaseInterface":"cli","liquibaseVersion":"DEV","md5Sum":"9:0160e0cb8fe825cbd40207ef539e0d08","outcome":"success","start":"2024-01-16 16:42:20.208","systemUser":"liquibase-user","tag":"null"},{"arguments":"--dbclhistory-enabled=true --license-key ***** update","author":"other.dev","command":"update","comments":"example-comment","contexts":"example-context","deploymentId":"5441340119","description":"addColumn tableName=person","end":"2024-01-16 16:42:20.26","executedSql":"ALTER TABLE PUBLIC.person ADD country VARCHAR(2);","extensions":"internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal...","filename":"example-changelog.xml","hostname":"LAPTOP-74GFS93J","id":"3","internalCommand":"update","labels":"example-label","liquibaseInterface":"cli","liquibaseVersion":"DEV","md5Sum":"9:cf75e37ee64b860fb5d1d1bc943c75fb","outcome":"success","start":"2024-01-16 16:42:20.249","systemUser":"liquibase-user","tag":"null"}]Liquibase command 'dbcl-history' was executed successfully.
[
  {
    "arguments": "--dbclhistory-enabled=true --license-key ***** update",
    "author": "your.name",
    "command": "update",
    "comments": "example-comment",
    "contexts": "example-context",
    "deploymentId": "5441340119",
    "description": "createTable tableName=person",
    "end": "2024-01-16 16:42:20.158",
    "executedSql": "CREATE TABLE PUBLIC.person (id INT GENERATED BY DEFAULT AS IDENTITY NOT NULL, name VARCHAR(50) NOT NULL, address1 VARCHAR(50), address2 VARCHAR(50), city VARCHAR(30), CONSTRAINT PK_PERSON PRIMARY KEY (id));",
    "extensions": "internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal...",
    "filename": "example-changelog.xml",
    "hostname": "LAPTOP-74GFS93J",
    "id": "1",
    "internalCommand": "update",
    "labels": "example-label",
    "liquibaseInterface": "cli",
    "liquibaseVersion": "DEV",
    "md5Sum": "9:884ea70a8e61427b7b1a217a62954c48",
    "outcome": "success",
    "start": "2024-01-16 16:42:20.144",
    "systemUser": "liquibase-user",
    "tag": "null"
  },
  {
    "arguments": "--dbclhistory-enabled=true --license-key ***** update",
    "author": "your.name",
    "command": "update",
    "comments": "example-comment",
    "contexts": "example-context",
    "deploymentId": "5441340119",
    "description": "createTable tableName=company",
    "end": "2024-01-16 16:42:20.216",
    "executedSql": "CREATE TABLE PUBLIC.company (id INT GENERATED BY DEFAULT AS IDENTITY NOT NULL, name VARCHAR(50) NOT NULL, address1 VARCHAR(50), address2 VARCHAR(50), city VARCHAR(30), CONSTRAINT PK_COMPANY PRIMARY KEY (id));",
    "extensions": "internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal...",
    "filename": "example-changelog.xml",
    "hostname": "LAPTOP-74GFS93J",
    "id": "2",
    "internalCommand": "update",
    "labels": "example-label",
    "liquibaseInterface": "cli",
    "liquibaseVersion": "DEV",
    "md5Sum": "9:0160e0cb8fe825cbd40207ef539e0d08",
    "outcome": "success",
    "start": "2024-01-16 16:42:20.208",
    "systemUser": "liquibase-user",
    "tag": "null"
  },
  {
    "arguments": "--dbclhistory-enabled=true --license-key ***** update",
    "author": "other.dev",
    "command": "update",
    "comments": "example-comment",
    "contexts": "example-context",
    "deploymentId": "5441340119",
    "description": "addColumn tableName=person",
    "end": "2024-01-16 16:42:20.26",
    "executedSql": "ALTER TABLE PUBLIC.person ADD country VARCHAR(2);",
    "extensions": "internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal...",
    "filename": "example-changelog.xml",
    "hostname": "LAPTOP-74GFS93J",
    "id": "3",
    "internalCommand": "update",
    "labels": "example-label",
    "liquibaseInterface": "cli",
    "liquibaseVersion": "DEV",
    "md5Sum": "9:cf75e37ee64b860fb5d1d1bc943c75fb",
    "outcome": "success",
    "start": "2024-01-16 16:42:20.249",
    "systemUser": "liquibase-user",
    "tag": "null"
  }
]
Liquibase command 'dbcl-history' was executed successfully.

By default, Liquibase limits the length of the extensions and sql keys to 500 characters. You can specify --verbose to show the full strings.

[
  {
    "arguments": "--dbclhistory-enabled=true --license-key ***** update",
    "author": "your.name",
    "command": "update",
    "comments": "example-comment",
    "contexts": "example-context",
    "deploymentId": "5441340119",
    "description": "createTable tableName=person",
    "end": "2024-01-16 16:42:20.158",
    "executedSql": "CREATE TABLE PUBLIC.person (id INT GENERATED BY DEFAULT AS IDENTITY NOT NULL, name VARCHAR(50) NOT NULL, address1 VARCHAR(50), address2 VARCHAR(50), city VARCHAR(30), CONSTRAINT PK_PERSON PRIMARY KEY (id));",
    "extensions": "internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal\\lib\\jaxb-core.jar: JAXB Core 4.0.4 By Eclipse Foundation, internal\\lib\\jaxb-runtime.jar: JAXB Runtime 4.0.4 By Eclipse Foundation, internal\\lib\\jaybird.jar: Jaybird 5.0.2.java8 (build: variant=jaybird tag=v5.0.2 date=202306070943) By Firebird project, internal\\lib\\jcc.jar: IBM JCC JDBC 4 Driver 1.4.0 By IBM, internal\\lib\\liquibase-commercial.jar: Commercial Liquibase Functionality DAT-16388-SNAPSHOT By Liquibase, internal\\lib\\mariadb-java-client.jar: mariadb-java-client 3.2.0 By mariadb.com, internal\\lib\\mssql-jdbc.jar: Microsoft JDBC Driver for SQL Server 12.4.1 By Microsoft Corporation, internal\\lib\\ojdbc8.jar: JDBC 19.21.0.0.0 By Oracle Corporation, internal\\lib\\opencsv.jar: opencsv 5.9.0, internal\\lib\\picocli.jar: picocli 4.7.5 By Remko Popma, internal\\lib\\postgresql.jar: PostgreSQL JDBC Driver 42.7.1 By PostgreSQL Global Development Group, internal\\lib\\snakeyaml.jar: SnakeYAML 2.2.0, internal\\lib\\snowflake-jdbc.jar: snowflake-jdbc 3.14.3, internal\\lib\\sqlite-jdbc.jar: SQLite JDBC 3.44.1.0",
    "filename": "example-changelog.xml",
    "hostname": "LAPTOP-74GFS93J",
    "id": "1",
    "internalCommand": "update",
    "labels": "example-label",
    "liquibaseInterface": "cli",
    "liquibaseVersion": "DEV",
    "md5Sum": "9:884ea70a8e61427b7b1a217a62954c48",
    "outcome": "success",
    "start": "2024-01-16 16:42:20.144",
    "systemUser": "liquibase-user",
    "tag": "null"
  },
  {
    "arguments": "--dbclhistory-enabled=true --license-key ***** update",
    "author": "your.name",
    "command": "update",
    "comments": "example-comment",
    "contexts": "example-context",
    "deploymentId": "5441340119",
    "description": "createTable tableName=company",
    "end": "2024-01-16 16:42:20.216",
    "executedSql": "CREATE TABLE PUBLIC.company (id INT GENERATED BY DEFAULT AS IDENTITY NOT NULL, name VARCHAR(50) NOT NULL, address1 VARCHAR(50), address2 VARCHAR(50), city VARCHAR(30), CONSTRAINT PK_COMPANY PRIMARY KEY (id));",
    "extensions": "internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal\\lib\\jaxb-core.jar: JAXB Core 4.0.4 By Eclipse Foundation, internal\\lib\\jaxb-runtime.jar: JAXB Runtime 4.0.4 By Eclipse Foundation, internal\\lib\\jaybird.jar: Jaybird 5.0.2.java8 (build: variant=jaybird tag=v5.0.2 date=202306070943) By Firebird project, internal\\lib\\jcc.jar: IBM JCC JDBC 4 Driver 1.4.0 By IBM, internal\\lib\\liquibase-commercial.jar: Commercial Liquibase Functionality DAT-16388-SNAPSHOT By Liquibase, internal\\lib\\mariadb-java-client.jar: mariadb-java-client 3.2.0 By mariadb.com, internal\\lib\\mssql-jdbc.jar: Microsoft JDBC Driver for SQL Server 12.4.1 By Microsoft Corporation, internal\\lib\\ojdbc8.jar: JDBC 19.21.0.0.0 By Oracle Corporation, internal\\lib\\opencsv.jar: opencsv 5.9.0, internal\\lib\\picocli.jar: picocli 4.7.5 By Remko Popma, internal\\lib\\postgresql.jar: PostgreSQL JDBC Driver 42.7.1 By PostgreSQL Global Development Group, internal\\lib\\snakeyaml.jar: SnakeYAML 2.2.0, internal\\lib\\snowflake-jdbc.jar: snowflake-jdbc 3.14.3, internal\\lib\\sqlite-jdbc.jar: SQLite JDBC 3.44.1.0",
    "filename": "example-changelog.xml",
    "hostname": "LAPTOP-74GFS93J",
    "id": "2",
    "internalCommand": "update",
    "labels": "example-label",
    "liquibaseInterface": "cli",
    "liquibaseVersion": "DEV",
    "md5Sum": "9:0160e0cb8fe825cbd40207ef539e0d08",
    "outcome": "success",
    "start": "2024-01-16 16:42:20.208",
    "systemUser": "liquibase-user",
    "tag": "null"
  },
  {
    "arguments": "--dbclhistory-enabled=true --license-key ***** update",
    "author": "other.dev",
    "command": "update",
    "comments": "example-comment",
    "contexts": "example-context",
    "deploymentId": "5441340119",
    "description": "addColumn tableName=person",
    "end": "2024-01-16 16:42:20.26",
    "executedSql": "ALTER TABLE PUBLIC.person ADD country VARCHAR(2);",
    "extensions": "internal\\lib\\commons-collections4.jar: Apache Commons Collections 4.4.0 By The Apache Software Foundation, internal\\lib\\commons-lang3.jar: Apache Commons Lang 3.13.0 By The Apache Software Foundation, internal\\lib\\commons-text.jar: Apache Commons Text 1.11.0 By The Apache Software Foundation, internal\\lib\\h2.jar: H2 Database Engine 2.2.224 By H2 Group, internal\\lib\\hsqldb.jar: HSQLDB 2.7.2 By The HSQL Development Group, internal\\lib\\jaxb-api.jar: jaxb-api 2.3.1 By Oracle Corporation, internal\\lib\\jaxb-core.jar: JAXB Core 4.0.4 By Eclipse Foundation, internal\\lib\\jaxb-runtime.jar: JAXB Runtime 4.0.4 By Eclipse Foundation, internal\\lib\\jaybird.jar: Jaybird 5.0.2.java8 (build: variant=jaybird tag=v5.0.2 date=202306070943) By Firebird project, internal\\lib\\jcc.jar: IBM JCC JDBC 4 Driver 1.4.0 By IBM, internal\\lib\\liquibase-commercial.jar: Commercial Liquibase Functionality DAT-16388-SNAPSHOT By Liquibase, internal\\lib\\mariadb-java-client.jar: mariadb-java-client 3.2.0 By mariadb.com, internal\\lib\\mssql-jdbc.jar: Microsoft JDBC Driver for SQL Server 12.4.1 By Microsoft Corporation, internal\\lib\\ojdbc8.jar: JDBC 19.21.0.0.0 By Oracle Corporation, internal\\lib\\opencsv.jar: opencsv 5.9.0, internal\\lib\\picocli.jar: picocli 4.7.5 By Remko Popma, internal\\lib\\postgresql.jar: PostgreSQL JDBC Driver 42.7.1 By PostgreSQL Global Development Group, internal\\lib\\snakeyaml.jar: SnakeYAML 2.2.0, internal\\lib\\snowflake-jdbc.jar: snowflake-jdbc 3.14.3, internal\\lib\\sqlite-jdbc.jar: SQLite JDBC 3.44.1.0",
    "filename": "example-changelog.xml",
    "hostname": "LAPTOP-74GFS93J",
    "id": "3",
    "internalCommand": "update",
    "labels": "example-label",
    "liquibaseInterface": "cli",
    "liquibaseVersion": "DEV",
    "md5Sum": "9:cf75e37ee64b860fb5d1d1bc943c75fb",
    "outcome": "success",
    "start": "2024-01-16 16:42:20.249",
    "systemUser": "liquibase-user",
    "tag": "null"
  }
]
Liquibase command 'dbcl-history' was executed successfully.