-
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
Fixed issue with h2 loadUpdateData not correctly handling values with the string " values " in the inserted data #1831
Conversation
Hi @tomyy
The PR will be prioritized according to our internal development and testing capacity. We’ll let you know when it’s ready to move to the next step or if any changes are needed. |
How can I trigger a rebuild? The "Build and Test / Java 11" failed because some dependencies could not be resolved, but my code change doesn't change any dependencies... |
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.
Code review and test results:
Things to be aware of:
- Change fixes regular expression to use the first " values " it finds in a statement as the "values" part of the SQL vs. the last " values " it finds which might be in some of the inserted data.
- Adds a unit test for a problem "values" statement
- Only impacts H2
Things to worry about:
- Nothing
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.
PR fixes and H2 bug caused by having the key word "values" in the data of a loadData changetype.
- New unit test added to validate the fix.
APPROVED
Note: There were test harness failures for EDB Postgres; these are unrelated to this fix and were due to the EDB environment not loading correctly.
Thanks for your PR submission! We just finished reviewing and merging it into the 4.17.0 release on October 10, 2022. When you get a chance, could you please Star the Liquibase project? The star button is in the upper right corner of the screen. |
1 similar comment
Thanks for your PR submission! We just finished reviewing and merging it into the 4.17.0 release on October 10, 2022. When you get a chance, could you please Star the Liquibase project? The star button is in the upper right corner of the screen. |
Environment
Liquibase Version: all
Liquibase Integration & Version: all
Liquibase Extension(s) & Version:
Database Vendor & Version: H2
Operating System Type & Version: all
Pull Request Type
Description
(Copied from #1767)
Here is the description with a workaround:
https://forum.liquibase.org/t/cant-insert-the-string-scale-values-mean-without-it-being-changed/5121
Steps To Reproduce
Actual Behavior
Changeset rendered:
-- Changeset db.changelog-master.yaml::1595012255439-41::myarbrou
-- WARNING The following SQL may change each run and therefore is possibly incorrect and/or invalid:
MERGE INTO PUBLIC.usage_agreement_terms (version, text, start_date) VALUES ('v1.0', 'scale KEY(version) values mean', '2021-02-12');
Expected/Desired Behavior
Changeset should be:
-- Changeset db.changelog-master.yaml::1595012255439-41::myarbrou
-- WARNING The following SQL may change each run and therefore is possibly incorrect and/or invalid:
MERGE INTO PUBLIC.usage_agreement_terms (version, text, start_date) KEY(version) VALUES ('v1.0', 'scale values mean', '2021-02-12');
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
Fast Track PR Acceptance Checklist:
Need Help?
Come chat with us on our discord channel