changelog Parameters

Since Liquibase 1.7

Liquibase allows dynamic substitution of parameters in a changelog. The parameters to replace are described using the ${parameter-name} syntax.

Configuring parameter values

Parameter values are looked up in the following order:

  1. Passed as a parameter to your Liquibase runner (see Ant, Maven, Servlet Listener) etc. documentation for how to pass them)
  2. As a JVM system property
  3. As an environment variable
  4. Command Line Interface parameter if executed from the command line
  5. properties file if used or executed from the command line
  6. In the parameters block (property element) of the DATABASECHANGELOG file itself

Once a parameter its value cannot be changed, only the first definition is used, other are skipped.

XML example


    <property  name="clob.type"  value="clob"  dbms="oracle,postgresql"/>  
    <property  name="clob.type"  value="longtext"  dbms="mysql"/>  
    <property  name=""  value="tableA"/>  

    <changeSet  id="1"  author="joe">  
         <createTable  tableName="${}">  
             <column  name="id"  type="int"/>  
             <column  name="${}"  type="${clob.type}"/>  
             <column  name="${}"  type="int"/>  

YAML example

  -  property:  
      dbms:  oracle,postgresql  
      name:  clob.type  
      value:  clob  
  -  property:  
      dbms:  mysql  
      name:  clob.type  
      value:  longtext  
  -  property:  
      value:  tableA  
  -  changeSet:  
      id:  1  
      author:  joe  
      -  createTable:  
          tableName:  ${}  
          -  column:  
              name:  id  
              type:  int  
          -  column:  
              name:  ${}  
              type:  "${clob.type}  
              defaultValue:  a  string  with  an  ${undefined.param}  param  against  ${dbNote}  
          -  column:  
              name:  ${}  
              type:  int


Defines a parameter for the changelog. Given a list of contexts and/or databases, the parameter will be only used in those contexts and/or databases.

Available attributes

Attribute Description
name Name of the parameter. Required if file is not set
value Value of the of the property. required if file is not set
file Name of the file the properties shall be loaded from. It will create a property for all properties in the file. The content of the file has to follow the java properties file format
context Contexts the property is valid in. Expected as comma separated list.
dbms The type of a database which that property is to be used. When the migration step is running, it checks the database type against this attribute. Valid database type names are listed on the supported databases page. It is possible to list multiple databases separated by commas. You can also specify that a changeset is NOT applicable to a particular database type by prefixing with !. The keywords all and none are also available.
global Boolean. Defines whether the property is global or limited to the actual DATABASECHANGELOG. Given as "true" or "false".


    <property  name="simpleproperty"  value="somevalue"/>  
    <property  name="clob.type"  value="clob"  dbms="oracle,h2"/>  
    <property  name="clob.type"  value="longtext"  dbms="mysql"/>  
    <property  name="myproperty"  value="yes"  context="common,test"/>  
    <property  name="localproperty"  value="foo"  global="false"/>