We are seeing the same situation. Here is our situation, we have a stored procedure that is loaded in it’s own changeset. This stored procedure has been around for awhile now. Recently, it has changed and is ready to be released. Along with this change we were trying to migrate from 2.0.5 to 3.2.2. The behavior we saw is the same as mentioned above. We see the checksum being updated, but the changeset is not being executed. Even though, the stored procedure has changed. It’s almost as if liquibase is blankedly changing the checksum and not validating that the changeset has changed. Is there a migration path we should follow? Meaning we should migrate to 3.0.1, then to 3.1.0, then to 3.2.2?
Here is some information we were able to obtain. It’s not much, but it is all we found at the moment.
MD5SUM from 2.0.5:
3:076966900dcf8b4ff10930d4307aef1e
MD5SUM after 3.2.2 Upgrade:
7:51fd8131bc28f437fa60a0ca5e9fda45
What comes out in log files:
2014-08-18 16:57:53,964 DEBUG [liquibase] [main]: Computed checksum for 7:4fdb820696b1ca7c77783fbea3139fe3: as 51fd8131bc28f437fa60a0ca5e9fda45
2014-08-18 16:57:53,964 DEBUG [liquibase] [main]: Executing EXECUTE database command: UPDATE LIQUIBASE_{db user} SET MD5SUM = ‘7:51fd8131bc28f437fa60a0ca5e9fda45’ WHERE ID=‘{changeset-id}’ AND AUTHOR=‘{author}’ AND FILENAME=‘{filename}’
…
…
2014-08-18 16:57:56,174 DEBUG [liquibase] [main]: {filename}: {parent filename}::{changeset id}::{author}: Computed checksum for inputStream as 4fdb820696b1ca7c77783fbea3139fe3