change set logged as executed but actually not executed

General Discussion
1

Hi,

We have used Liquibase for a few years now and are quite happy with the tool. We have encountered the following situation a couple of times in our most recent database migration scripts though: a change set is logged in the databasechangelog table as executed but in reality, it wasn’t executed. The 2 change sets are simple blocks, with simple insert or update statements.

We use the 1.9 version of Liquibase.

As anyone encountered something similar?

Thanks a lot

Etienne

2

No, I have not seen it. Any preconditions or reasons the statements would have failed?

Nathan

3

If you add logLevel=DEBUG, does it output anything helpful?

Nathan

4

I’ll try that and see out it goes. Thanks.

Etienne

5

None that I can think of. We use MySQL as our database and when we execute the sql statements in the MySQL console, they’re executed just fine.

Etienne