I have a job that runs in “paranoid” mode, to do all possible checks I can think of, before I let the next step (update) start.
So it does
liquibase validate, but in some cases I get an error like:
2 change sets have changed since they were ran against the database
The strange thing is that just a few minutes earlied I “ran” these changes with
liquibase changelogSync successfully. Here’s the scenario:
added some new changesets
liquibase validate => validation error
Any idea why? In the “paranoia” mode checks should I run validate or not? Does updateSQL fail if someone changed a changeset that already ran?