GenerateChangeLog and Composite Foreign Keys

Has anyone had trouble using Liquibase generateChangeLog with composite foreign keys? My application uses composite keys. When I try to apply the changelog created by generateChangeLog, my foreign keys all fail because they cannot find the primary key. The primary key cannot be found because the foreign key is looking for a single field primary key when in fact, it should be a composite primary key?

Has anyone else experienced this? Is there a JIRA issue related that I could have a look at?

We did a little diff improvement for 2.0, but I don’t think we’ve attempted to fix compound FKs yet.  The plan is to look more into the diff too for the liquibase 2.1 timeframe.

There is which is currently unresolved.