We are upgrading from Liquibase 3.3.2 to version 4.4.3.
We have a Postgres database created from changesets defined in Liquibase 3.3.2. Running the version 3.3.2
validate command against this database and pointing to our master changelog file shows the message “No validation errors found” - as expected.
However, running the equivalent
validate command using the 4.4.3 version of Liquibase against the same Postgres database and same master changelog file shows the message “300 change sets have changed since they were ran against the database”. (NB: There have been no database changes (new changesets) in between running the two commands.)
$ liquibase-4.4.3\liquibase.bat --changelog-file=masterChangeLog.xml --url=jdbc:postgresql://localhost:38000/[databaseName] --driver-properties-file=liquibase.properties validate Starting Liquibase at 15:38:40 (version 4.4.3 #53 built at 2021-08-05 18:32+0000) Liquibase Version: 4.4.3 Liquibase Community 4.4.3 by Datical Validation Error: 300 change sets have changed since they were ran against the database ChangeLog-6.1.0.xml::[changesetName1]::[username] was: 7:b135dc4c148a772d6c6f9b65eb8f81ab but is now: 8:745d7f24706f71f4ebe37973afde398c ChangeLog-6.1.0.xml::[changesetName2]::[username] was: 7:cb6cb2cd402ae5193748eb82a872d9ba but is now: 8:71adf6ff457d112cc15f83e16de5dc92 ...etc. ...etc.
I have noticed that there appears to be some sort of algorithm version change in the
md5sum before and after values, e.g.
How should I proceed before using the 4.4.3 version of the