...
The checksum however, remained the same as previous.
To work around this and prevent the below issue on duplicate liquibase steps being attempted, you can add the "logicalFilePath" attribute in the changeSet. This essentially points it to the original changeset file, thus keeps track by using the same entry in the databasechangelog database, instead of creating a new one.
Duplicate liquibase steps:
We do however encounter a different issue. Because a new (checksum) entry is added to the table, liquibase cannot see that nothing changed when the step was previously applied.
It therefore tries to reapply some steps, resulting in errors such as "column does not exist".
This is because when trying to rename a column, the old column name no longer exists.
To work around this, I added a "preCondition" to any impacted changeSet, to check that a column, index etc exists first, before we apply the relevant step.
Initial NCMP data:
Previously, liquibase added some NCMP data such as and the model loader subsequently expected it to be there.
...
Hence some additions to the NCMP ModelLoader to ensure some initial data exists.
Remaining Questions:
...