-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fetch ran change sets before updating check sums #4762
Fetch ran change sets before updating check sums #4762
Conversation
@hpoettker interesting, this change is causing some tests to fail. I'm trying to figure out why.. any ideas? |
@filipelautert Do you mean the integration tests for Oracle and MariaDB? That is indeed curious. Both tests are failing when creating the sequence
I'd say that the I don't see how my proposed change could cause such a problem. I also don't see how I can easily reproduce the test setup for the integration tests. |
I found the yaml to get the integration tests working locally. 😄 The original PR was indeed erroneous. Using the constructor of I've also amended |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, good idea to fix it on ValidatingVisitor. In fact the Visitor is becoming a "fix it all" Visitor - something to think about .
@rberezen functional tests are passing here -> https://github.com/liquibase/liquibase-pro-tests/actions/runs/6038104842
Impact
Description
Fixes #4460.
The fix ensures that the field
storedFilePath
for eachchangeSet
inUpdateChangeSetChecksumGenerator
is set. Then, theWHERE
condition of the producedUPDATE
statements matches the database entry for the respective change set.Things to be aware of
Things to worry about
Additional Context