While using LiquiBase to generateChangeLog for a large DB2 database, I noticed that one particular schema took way longer than the others (we have about 60 schemas). The one that took longer makes heavy use of aliases to point to tables in other schemas. However, LiquiBase extracts these aliases as full tables - meaning that in the generated XML file, it puts createTable entries in for each alias. While this would technically produce a correct schema, the objects that were aliases will be empty.
Anybody have any ideas how to work around this?
I would have hoped for a entry or similar.