The --global-end-delimiter argument is similar to the endDelimiter attribute for the sql, sqlFile, partiql, and partiqlFile Change Types, but has a global scope.

If you set--global-end-delimiter and do not set endDelimiter, then Liquibase applies the value of --global-end-delimiter to all changesets. If you set a delimiter both ways, Liquibase determines which delimiter to use for a changeset in the following order:

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

2. endDelimiter set in a changelog called by include or includeAll in modifyChangeSets

3. --global-end-delimiter set globally (lowest precedence)

You can give --global-end-delimiter the highest precedence of all delimiter settings by also using the --global-end-delimeter-override parameter.

It is a best practice not to use --global-end-delimiter on changesets you are running with a native executor. Native executors handle delimiters natively.

Uses

If you need to deploy SQL using a non-standard delimiter, such as if the SQL you're deploying contains the ; character, you can use --global-end-delimiter to set a custom delimiter across all your changesets. This is easier than manually specifying endDelimiter on every individual changeset. Also, having one central parameter for a delimiter reduces inconsistencies resulting from manual updates to changesets.

Syntax

You can set this parameter in the following ways:

For more information, see Working with command parameters.

Command history