I'm using Liquibase to update my database from two sides:
Via the Liquibase Maven plugin
Via Spring with SpringLiquibase that updates the database upon application startup
Running vacuum from the db-changelog-master.xml like the following code snippet works for now. (By setting validCheckSum to ANY. But without it database updates only succeed when run from one of the two sides described above. F.i. when it has run via SpringLiquibase, and is run again via SpringLiquibase, all is fine. Checksum is ok. But when I then update the database via Maven a checksum error occurs. The checksum is different when run from Maven then when run from SpringLiquibase.
Maybe it has something do with logicalFilePath. Without it, it seems to run ok, but then I run into other issues with Spring filename path using classpath:... etc..
Using: Java 7, Postgresql 9.4 with postgis, Spring 4.1.6, Liquibase 3.3.3, Liquibase-spacial 1.2.1, liquibase-postgresql 3.0
I'm using Liquibase to update my database from two sides:
Running vacuum from the db-changelog-master.xml like the following code snippet works for now. (By setting validCheckSum to ANY. But without it database updates only succeed when run from one of the two sides described above. F.i. when it has run via SpringLiquibase, and is run again via SpringLiquibase, all is fine. Checksum is ok. But when I then update the database via Maven a checksum error occurs. The checksum is different when run from Maven then when run from SpringLiquibase.
Maybe it has something do with logicalFilePath. Without it, it seems to run ok, but then I run into other issues with Spring filename path using classpath:... etc..
Using: Java 7, Postgresql 9.4 with postgis, Spring 4.1.6, Liquibase 3.3.3, Liquibase-spacial 1.2.1, liquibase-postgresql 3.0
Note: Same checksum error occurs when using another extension, liquibase-spatial. With this extension specifically on the creation of a spatial index. See https://github.com/lonnyj/liquibase-spatial/issues/7
File db-changelog-master.xml:
Spring config:
Snippet db-changelog-spacial-example.xml:
┆Issue is synchronized with this Jira Bug by Unito