Checksum changed between liquibase 3.0.4 and liquibase 3.0.5 - suggestion for error message

Liquibase Development
1

We have a changeset applied to production via liquibase 3.0.4.  Using newer versions of liquibase we can’t apply later changeset because the check sum is different for different liquibase versions.  It is specific to this changeset - others are fine.

Changeset

  1.    
  2.        
  3.            
  4.             TYPE_ID=‘INFLATION_VOLS’
  5.        
  6.    

Debug logging - liquibase 3.0.4

  1. DEBUG 06/12/13 13:29:liquibase: Computed checksum for update:[
  2.     columns=[
  3.         [
  4.             name=“CAT_2”
  5.             value=“Impact of Volatilities”
  6.         ]
  7.     ]
        tableName=“PNL_ATTRIB_TYPE”
  8.     whereClause=“TYPE_ID=‘INFLATION_VOLS’”
  9. ] as febf5cd7dc52e773fa62bff547ac5203
  10. DEBUG 06/12/13 13:29:liquibase: Computed checksum for 7:febf5cd7dc52e773fa62bff547ac5203: as 083928d50177aec8a6a073355be9b15b

Debug logging - liquibase 3.0.7

  1. DEBUG 06/12/13 13:29:liquibase: Computed checksum for update:[
  2.     columns=[
  3.         [
  4.             name=“CAT_2”
  5.             value=“Impact of Volatilities”
  6.         ]
  7.     ]
  8.     tableName=“PNL_ATTRIB_TYPE”
  9.     where=“TYPE_ID=‘INFLATION_VOLS’”
  10. ] as b0dda9b1838ffb6348307fd9dfd18d78
  11. DEBUG 06/12/13 13:29:liquibase: Computed checksum for 7:b0dda9b1838ffb6348307fd9dfd18d78: as a45c6787b90dee195944be8f0cc651ff
  12. Liquibase updateSql Failed: Validation Failed:
  13.      1 change sets check sum
  14.           upgrades/changelog.f-3.9.1.xml::Correct INFLATION_VOLS Typo::Barney is now: 7:a45c6787b90dee195944be8f0cc651ff

The changeset’s ‘where’ has changed from ‘whereClause’ to ‘where’ in liquibase 3.0.5.

I understand there is no guarantee that check sums won’t change between liquibase versions, from other posts in this forum. How about if liquibase highlights version differences (from DATABASECHANGELOG.LIQUIBASE) in this situation - i.e. the error message should state that the changeset was applied with a different version of liquibase, and could now be failing because of liquibase version differences, not because the changeset itself has changed.