Add db-migrations-flyway-liquibase: Flyway vs Liquibase migrations, rollbacks and baselines on Spring Boot 4.1

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
2026-09-15 07:08:57 +00:00
parent b02fbe1416
commit 3908331431
61 changed files with 3128 additions and 0 deletions
@@ -0,0 +1,22 @@
+==================================================
+Flyway: adopting an existing, unmanaged schema
+==================================================
+captured: 2026-09-15T07:07:29.126413637Z
+
+
+-- migrate() with no baseline configuration, against a non-empty schema --
+FlywayException: Found non-empty schema(s) "PUBLIC" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
+
+-- migrate() with baselineOnMigrate=true, baselineVersion=1 --
+installed_rank | version | description                               | type     | success
+---------------+---------+-------------------------------------------+----------+--------
+-1             | NULL    | << Flyway Schema History table created >> | TABLE    | true   
+1              | 1       | pre-flyway schema                         | BASELINE | true   
+2              | 2       | add status column                         | SQL      | true   
+(3 rows)
+
+-- legacy_account keeps its pre-existing row and gains the new column --
+ID | OWNER           | STATUS
+---+-----------------+-------
+1  | pre-flyway-data | ACTIVE
+(1 row)