--include-objects

Dependent objects and columns the filter leaves out

If your filter includes a foreign key but leaves out the column it references, the foreign key stays in the output of diff, diff-changelog, and generate-changelog without that column. The same applies to a unique constraint, primary key, or index that uses a column the filter leaves out. A changelog generated this way can fail to deploy, because those objects reference a column the changelog never creates.

Liquibase warns you when this happens. The warning is a count of the affected objects, not a list:

WARNING: 4 object(s) depend on a column excluded by --excludeObjects/--includeObjects. The diff or generated changelog may reference an object that does not exist and could fail to deploy. See the log for details.

The warning does not change the output. The command still completes, and diff-changelog and generate-changelog still write the changelog with those objects in it. Review the changelog and remove or correct the dependent objects before you deploy it.

To see which objects are affected, set --log-level to WARNING or a more verbose level. Each object is logged on its own line, naming the object and the column it depends on:

liquibase diff-changelog --include-objects="<string>" --log-level=WARNING --log-file=liquibase.log

Note: Liquibase detects foreign keys, unique constraints, primary keys, and indexes, because it knows which columns they use. It does not detect a view, function, stored procedure, or trigger whose SQL references the column, so these objects get no warning. A function or procedure like this can deploy without an error and fail only when it runs, so check them yourself.

Syntax

You can set this parameter in the following ways: