liquibase 3 checksums

General Discussion
1

When I run liquibase 3.0 conversions against databases that I updated with liquibase 2.0.5 I often get checksum errors of the format.

file1::id001::me is now: 7:acd3c6774dd4ba2823bea5181922dadb

in almost every case the original checksum began with 3: and the new checksum is different and begines with 7:

Should I expect the sums to be different and, if so, can I fix it by simply nulling the md5sum column?

2

The “#:” is a prefix liquibase adds to know if the checksum changed or the whole algorithm changed. Unfortunately the algorithm changed from 2.x to 3.x so they will all be different. If you do a liquibase update it will automatically replace them due to the version change, or you can null them out.


Nathan