I have 2 projects that use Liquibase and found that 1 project fails to 'validate' the database on startup when a commandline script was used to update and even when commandline script executed from different path. The project that works has a master xml that includes a changelog xml and the project that fails only has a changelog xml file. I found I could reproduce the problem easily by creating the database schema from one path and then executing same script with another path one being absolute path and the other relative. This leads me to believe the checksum is calculated using the full path of changelog file. I would expect that only the content of the changeset should be used in checksum and not the path to the file.
I have 2 projects that use Liquibase and found that 1 project fails to 'validate' the database on startup when a commandline script was used to update and even when commandline script executed from different path.
The project that works has a master xml that includes a changelog xml and the project that fails only has a changelog xml file.
I found I could reproduce the problem easily by creating the database schema from one path and then executing same script with another path one being absolute path and the other relative.
This leads me to believe the checksum is calculated using the full path of changelog file.
I would expect that only the content of the changeset should be used in checksum and not the path to the file.