Download 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: liquibase.command.tag.driver: The JDBC driver class Optional liquibase.command.driverPropertiesFile: liquibase.command.tag.driverPropertiesFile: The JDBC driver properties file Optional liquibase.command.password: liquibase.command.tag.password: Password to connect to the target database. Tip: ">Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. Optional liquibase.command.username: liquibase.command.tag.username: Username to connect to the target database. Tip: ">Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. Optional Attribute Definition Requirement JAVA_OPTS=-Dliquibase.command.tag= JAVA_OPTS=-Dliquibase.command.tag.tag= The tag identifying which tagged changesets in the changelog to evaluate. Specify as --tag=myTag. Positional format deprecated in 4.4+. Required JAVA_OPTS=-Dliquibase.command.url= JAVA_OPTS=-Dliquibase.command.tag.url= The JDBC database connection URL. See Using JDBC URL in Liquibase. Required JAVA_OPTS=-Dliquibase.command.addRow= JAVA_OPTS=-Dliquibase.command.tag.addRow= Liquibase Pro only. If true, creates a new DATABASECHANGELOG row for the tag you're adding. If false, adds the new tag to the last existing row. Liquibase 4.23.1+. Requires a Liquibase Pro license key. Default: false. Note: ">Note: If you create a new DATABASECHANGELOG row for your tag but later roll back that tag, Liquibase also rolls back the row you created. Optional JAVA_OPTS=-Dliquibase.command.defaultCatalogName= JAVA_OPTS=-Dliquibase.command.tag.defaultCatalogName= Name of the default catalog to use for the database connection Optional JAVA_OPTS=-Dliquibase.command.defaultSchemaName= JAVA_OPTS=-Dliquibase.command.tag.defaultSchemaName= 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: ">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: ">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

Tylor Graves December 23, 2024 16:32 Updated Applies toLiquibase ProLiquibase Open Source (Community)SummaryLiquibase is a versatile database change management tool that can be configured to deploy changes to multiple types of databases, such as Oracle and PostgreSQL, from a single instance. Below is a general guide to setting up Liquibase for this purpose.Environment ConditionsAny version of Liquibase Pro or Open SourceHow to Configure a Single Instance of Liquibase for Multiple DatabasesThis article will review two popular ways to configure a single instance of Liquibase to run on multiple databases. Liquibase Properties FilesStep 1: Create separate configuration files for each databaseExample for Oracle (liquibase.oracle.properties):changeLogFile=oracle_changelog.xmlurl=jdbc:oracle:thin:@//hostname:1521/service_nameusername=oracle_userpassword=oracle_passwordExample for PostgreSQL (liquibase.postgres.properties):changeLogFile=postgres_changelog.xmlurl=jdbc:postgresql://hostname:5432/database_nameusername=postgres_userpassword=postgres_passwordStep 2: Run Liquibase for Each DatabaseFor Oracle:liquibase --defaultsFile=liquibase.oracle.properties updateFor PostgreSQL:liquibase --defaultsFile=liquibase.postgres.properties updateCLI ArgumentsThe other alternative is to pass the required database information in as CLI arguments. liquibase \--changeLogFile=${CHANGELOG} \--url=${DB_URL} \--username=${DB_USERNAME} \--password=${DB_PASSWROD} \updateAll of the variables can be defined in the pipeline/environment. When Liquibase runs, it will deploy and connect to whatever database is given.This strategy is preferred when Liquibase runs inside a CI/CD platform. Related Article(s)N/A Related to

Note: ">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: ">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: "" } The JDBC driver class Optional cmdArgs: { driver-properties-file: "" } The JDBC driver properties file Optional cmdArgs: { password: "" } Password to connect to the target database. Tip: ">Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. Optional cmdArgs: { username: "" } Username to connect to the target database. Tip: ">Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. Optional Attribute Definition Requirement liquibase.command.tag: liquibase.command.tag.tag: The tag identifying which tagged changesets in the changelog to evaluate. Specify as --tag=myTag. Positional format deprecated in 4.4+. Required liquibase.command.url: liquibase.command.tag.url: The JDBC database connection URL. See Using JDBC URL in Liquibase. Required liquibase.command.addRow: liquibase.command.tag.addRow: Liquibase Pro only. If true, creates a new DATABASECHANGELOG row for the tag you're adding. If false, adds the new tag to the last existing row. Liquibase 4.23.1+. Requires a Liquibase Pro license key. Default: false. Note: ">Note: If you create a new DATABASECHANGELOG row for your tag but later roll back that tag, Liquibase also rolls back the row you created. Optional liquibase.command.defaultCatalogName: liquibase.command.tag.defaultCatalogName: Name of the default catalog to use for the database connection Optional liquibase.command.defaultSchemaName: liquibase.command.tag.defaultSchemaName: 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: ">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: ">Note: In Liquibase