Objects/Schema missing from generated SQL from diff-changelog command

Applies to

• Liquibase Secure (Pro)
• Liquibase Community (Open Source)

Issue Summary

When running diff-changelog and snapshot commands to generate a changelog based on the differences between two databases, some schemas are not included in the resulting generated SQL. A review of the Drift Report will indicate that all schemas are accounted for, but the changelog file will be missing objects.

Error Message

No error message is displayed while running the command, and it will display a successful completion.

Root Cause

When connecting to the database with a username that matches a schema name, a silent failure occurs while compiling the generated SQL, causing a schema to be skipped.

For example, connecting with username "workspace" while a schema of the same name, "workspace", exists in the database being used.

Resolution

Update Liquibase to v4.32.0+.

The latest releases can be found on Liquibase.com and GitHub.

Workaround

Connecting with a username that does not match a schema name should work around this issue until you're able to upgrade to version 4.32.0 or higher.