generateChangeLog does not create auto_increment correct with its unique key

General Discussion
1

Hi,


when using auto_increment (MySQL) in a column, the generateChangeLog splits the column- and the key-generation in 2 different change sets. That causes an error on migration:

“Incorrect table definition; there can be only one auto column and it must be defined as a key”


Dominik

2

What liquibase version are you using?

Nathan

3

Liquibase Version: 3.0.7

4

It works with my testing. Is it a multi-column primary key with one of them auto-increment? Can you send an example chagneSet?


Nathan

5

Added an example in a bug-report: CORE-1652 - generateChangeLog does not create auto_increment correct with its unique key

6

Thanks, I’ll take a look.


Nathan