2.0 RC6 breaks generateChangeLog by introducing "PRIMARY" index(es)


I just upgraded from RC5 to RC6 and found that my generated changelogs are broken. See below for an example.

The problem is, that

  • mysql does not want to create an index called PRIMARY
  • all single values primary keys get a generated PRIMARY-index
, so even if PRIMARY was a valid name, the creation would fail due to duplicate names.



The script is somewhat post-processed (e.g. adding autoIncrement="${autoIncrement}").

Is this behavior by design, or some last-minute bug?


It is a last minute bug (http://liquibase.jira.com/browse/CORE-732).  I’m looking into it.  Thanks for reporting it.