pro-global-end-delimiter-prioritized

--pro-global-end-delimiter-prioritized is a global Boolean parameter. It lets you specify whether the --pro-global-end-delimiter parameter always takes priority over other Liquibase delimiter settings. It is available in Liquibase 4.25.1 and later and requires a valid Liquibase Pro license key to use. The default value is false.

Uses

You can set a delimiter in Liquibase in the following ways:

  • endDelimiter set on a specific changeset, including in rollbackSqlFile (highest precedence)

  • endDelimiter set in a changelog called by include or includeAll in modifyChangeSets

  • --pro-global-end-delimiter set globally (lowest precedence)

By default, --pro-global-end-delimiter has the lowest precedence. This means that if you set it to some value (such as @), and you set endDelimiter to a different value (such as &), Liquibase uses the value of endDelimiter as your delimiter anywhere there is a conflict.

However, if you want Liquibase to always set delimiters based on --pro-global-end-delimiter no matter what, you can set --pro-global-end-delimiter-prioritized to true.

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.pro.globalEndDelimiter.prioritized: <true|false>

Global flow file argument

globalArgs: { pro-global-end-delimiter-prioritized: "<true|false>" }

Global CLI parameter

liquibase --pro-global-end-delimiter-prioritized=<true|false> update --changelog-file=example-changelog.xml

JVM system property (JAVA_OPTS environment variable)

Unix:

JAVA_OPTS=-Dliquibase.pro.globalEndDelimiter.prioritized=<true|false>

Windows:

JAVA_OPTS=-D"liquibase.pro.globalEndDelimiter.prioritized"=<true|false>

Liquibase environment variable

LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>

For more information, see Working with command parameters.