Allow previous Liquibase migration checksums for MariaDB #1352
Conversation
|
Excellent work @fxthomas. Maybe we can get one other person to confirm and then we should merge asap. |
|
@fxthomas thanks for your work. As mentioned in #1333, I replaced with docker cp the airsonic.war with yours https://github.com/fxthomas/airsonic/releases/tag/10.4.1-fix-1333. But seems the issue still exist for me: airsonic_10_4_1_fix.log. |
If someone was using MariaDB before airsonic#1188, they were probably doing so by using the MySQL JDBC driver to pass the migration (which had the proper workarounds in place for some column types). This commit assumes that the migrations done that way were valid and produced the same result as running the MariaDB migrations after airsonic#1188.
95db085 to
78a99d5
Compare
|
Ah, well, shoot, there were more changes not shown in the previous log! I'll make a new build in a sec, let me know if that one works for you. |
|
Done : can you download https://github.com/fxthomas/airsonic/releases/tag/10.4.1-fix-1333 again and test it? |
|
Thanks a lot!, now it works: airsonic_10_4_1_fix2.log |
|
Great, thank you for the quick updates! 😄 |
|
Fixed validation errors for me as well. |
|
Thank you! I don't use MariaDB/MySQL, so I cannot vouch for it unfortunately... That being said using the MariaDB driver for MariaDB is probably the safest, as they are developed together, right? |
If someone was using MariaDB before #1188, they were probably doing so by using the MySQL JDBC driver to pass the migration (which had the proper workarounds in place for some column types).
This commit assumes that the migrations done that way were valid and produced the same result as running the MariaDB migrations after #1188.
This should fix #1333.