This was because of a breaking change when migrating from liquibase 3.5.x to 3.6.x which happened due to this PR #16 . Reverting to spring boot 2.0.5 also fixes this but i think it's better to keep it updated.
There was a change in how the checksum logic is calculated and hence we need to use the exists clause for each database create query.
We also mark transaction as MARK_RAN so that liquibase will not try to run it again next if the pre-conditions fail.
Ok great. Thanks for looking into it. Never would have thought they would change the file names in major releases and spring boot will not account for it somehow.
Fixes #18
This was because of a breaking change when migrating from liquibase 3.5.x to 3.6.x which happened due to this PR #16 . Reverting to spring boot 2.0.5 also fixes this but i think it's better to keep it updated. There was a change in how the checksum logic is calculated and hence we need to use the exists clause for each database create query. We also mark transaction as
MARK_RAN
so that liquibase will not try to run it again next if the pre-conditions fail.