fix: upgrade path to develop branch

* With this naming of the flyway migration script, we can be sure that all of the migration scripts on the develop branch will run when upgrading from v74.5.x. When we used the same filename as on develop (V4_103__mysql_specific_align_collation.sql), then the migration script versions between 100 and 103 would not run. * This introduces a one-time log message after upgrading, which does not indicate a problem: ``` [2024-01-16T23:16:48.859776Z] uaa/uaa - 55182 [main] - [,] .... INFO --- JdbcTableSchemaHistory: Repairing Schema History table for version "4.101.0" (Marking as DELETED) . [2024-01-16T23:16:48.876250Z] uaa/uaa - 55182 [main] - [,] .... INFO --- DbRepair: Successfully repaired schema history table `uaa`.`schema_version` (execution time 00:00.11 6s). [2024-01-16T23:16:48.876398Z] uaa/uaa - 55182 [main] - [,] .... INFO --- DbRepair: Please ensure the previous contents of the deleted migrations are removed from the database, or moved into an existing migration. ``` Co-authored-by: Hongchol Sinn <[email protected]>
cloudfoundry · Jan 16, 2024 · 7985730 · 7985730
1 parent f90896e
commit 7985730
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 0 deletions.
diff --git a/...4_103__mysql_specific_align_collation.sql → ...101_0__mysql_specific_align_collation.sql b/...4_103__mysql_specific_align_collation.sql → ...101_0__mysql_specific_align_collation.sql
diff --git a/...4_103__mysql_specific_align_collation.sql → ...101_0__mysql_specific_align_collation.sql b/...4_103__mysql_specific_align_collation.sql → ...101_0__mysql_specific_align_collation.sql
diff --git a/...4_103__mysql_specific_align_collation.sql → ...101_0__mysql_specific_align_collation.sql b/...4_103__mysql_specific_align_collation.sql → ...101_0__mysql_specific_align_collation.sql