include-catalog-in-specification parameter is a Boolean that defines whether Liquibase includes the catalog name when determining equality between the compared databases. The default value is
false because you may want to compare the objects across two databases even though the catalogs are named differently in different environments.
If you run the diff command or the diff-changelog command with the
include-catalog-in-specification parameter set to
true, Liquibase will identify objects using both their object name and the catalog name.
Let’s say you have:
catalog1, which has the table
catalog2, which has the table
This way, Liquibase shows that there is a difference in the catalog name when executing the
diff command with
include-catalog-in-specification set to
true. For example, an object of
catalog1.my_schema.my_table is seen as a different object than
However, if you run the
diff command and do not specify
include-catalog-in-specification, Liquibase will not see any differences and identify only the database objects without checking if the catalog is the same.
You can set this parameter in the following ways:
|Liquibase properties file||
|Global flow file argument (example)||
|Global CLI parameter||
JVM system property (JAVA_OPTS Environment Variable)
|Liquibase Environment Variables||
For more information, see Working with Command Parameters.