Companion code for the Flyway vs Liquibase article: checksum validation, out-of-order and repeatable migrations, baselining an existing schema, Flyway Community's undo/diff/deploy stubs, concurrent-startup locking for both tools, Liquibase changeset identity and rollback (auto-generated vs explicit), a verified Liquibase 5.0.3 filename-caching defect, the new OSS license service, the FSL license change, and running both tools against one database. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Q6XdRjtsp4862EM44T7i9a
17 lines
856 B
Plaintext
17 lines
856 B
Plaintext
=====================================================
|
|
Flyway: editing an already-applied migration file
|
|
=====================================================
|
|
captured: 2026-09-15T07:07:27.074690371Z
|
|
|
|
|
|
-- first startup — V1 applied as originally written --
|
|
context started cleanly, V1__init.sql applied
|
|
|
|
-- second startup — V1__init.sql edited after being applied --
|
|
FlywayValidateException: Validate failed: Migrations have failed validation
|
|
Migration checksum mismatch for migration version 1
|
|
-> Applied to database : -712784830
|
|
-> Resolved locally : 756220147
|
|
Either revert the changes to the migration, or run repair to update the schema history.
|
|
Need more flexibility with validation rules? Learn more: https://help.red-gate.com/help/flyway-cli12/help_4.aspx?topic=flyway-blog/older-posts/customize-validation-rules-with-ignoremigrationpatterns
|