-
Notifications
You must be signed in to change notification settings - Fork 34
Update Liquibase to 4.5.x #1526
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
Comments
The migration on empty MySQL is failing now:
|
php-coder
added a commit
that referenced
this issue
Oct 25, 2021
After updating Liquibase version it's started to fail: 2 changes have validation failures columnDataType is required for setColumnRemarks on mysql, liquibase/version/0.4.4/2020-05-23--modify_condition_field.xml::modify-collections_series-condition-field::php-coder columnDataType is required for setColumnRemarks on mysql, liquibase/version/0.4.4/2020-05-23--modify_condition_field.xml::modify-series_sales-condition-field::php-coder Correction for 70c6f37 commit. Relate to #1526
php-coder
added a commit
that referenced
this issue
Sep 7, 2022
In the commit 4fd2d3b (#1526) the migrations have been updated in order to add a new required parameter. That broke the checksums. See https://www.liquibase.com/blog/what-affects-changeset-checksums Fix #1557
php-coder
added a commit
that referenced
this issue
Sep 8, 2022
…instead of the tables) comments In the commit 89ba68c (#1326) I used <setColumnRemarks> in order to put comments to the fields. It has turned out that on MySQL, Liquibase put comments on the tables instead of the fields (see liquibase/liquibase#942). After update of Liquibase (#1526), it became possible to fix the bug on our data. Fix #1408
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should be done after #1446
Changelogs:
The text was updated successfully, but these errors were encountered: