MD5SUM null when upgrading from 1.9.5 to 2.0-RC7

General Discussion
1

Hi all,
for a certain project I am trying to upgrade Liquibase from 1.9.5 to 2.0.-RC7 which works in general, but I get the MD5SUM=null for all old (->1.9.5) entries. Is this correct behaviour?
Frank

2

You mean you are getting a message like:

“INFO: Setting null checksum on changeSet changelogs/mysql/complete/root.changelog.xml::correct-mysql-timestamp::nvoxland::(Checksum: 3:0490d585e506ec8fe9025f8889213249) to correct value”

?

That would be the expected result.  We use a different checksum format between 1.9 and 2.0, and so you get that message alerting you that we are updating it.  I did make a change so it says “Updating null or out of date checksum on changeset…” to make it a little more understandable. 

Nathan

3

Hi Nathan,
the test case is as follows:

  1. Run some scripts with LB 1.9.5 (everything is fine!)

  2. Then switch the test build from 1.9.5 to 2.0-RC7

  3. And run another script (the script execution and its handling in the DATABASECHANGELOG table seem correct).

    Output of LB 2.0-RC7 (Ant):
    Buildfile: D:\test\buildLiquiBase_MigrationTest.xml
    update-MIGRATION:
    [updateDatabase] 11.11.2010 14:05:02 liquibase.logging.jvm.JavaUtilLogger info
    [updateDatabase] INFO: Successfully acquired change log lock
    [updateDatabase] 11.11.2010 14:05:03 liquibase.logging.jvm.JavaUtilLogger info
    [updateDatabase] INFO: Reading from DATABASECHANGELOG
    [updateDatabase] 11.11.2010 14:05:03 liquibase.logging.jvm.JavaUtilLogger info
    [updateDatabase] INFO: Reading from DATABASECHANGELOG
    [updateDatabase] 11.11.2010 14:05:03 liquibase.logging.jvm.JavaUtilLogger info
    [updateDatabase] INFO: ChangeSet test20rc7.xml::Test2.0-RC7::Frank ran successfully in 47ms
    [updateDatabase] 11.11.2010 14:05:03 liquibase.logging.jvm.JavaUtilLogger info
    [updateDatabase] INFO: Successfully released change log lock
    BUILD SUCCESSFUL
    Total time: 3 seconds

The MD5SUM column is NULL for all(!) entries which were inserted by LB 1.9.5 while the LB 2.0-RC7 entries seem ok. This is the outcome when running against Oracle 11g, MS SQL 2005, and DB2 9.7 databases.

Frank

4

Are the changeSets now null in databasechangelog still being referenced by the changelog you are running?  Or are they no longer in your changelog file passed to liquibase?  What happens is that it clears all changelog checksums when it detects an old version of the checksums, then updates it as it finds changesets.  If a changeset is no longer in the update script, it will remain with a null checksum.

Nathan