Hi everyone,
I'm encountering an issue with Flyway when managing migrations in PostgreSQL. Here's the situation:
![]()
2024-09-06 16:40:22.525 INFO 1 --- [ main] o.f.c.i.database.base.BaseDatabaseType : Database: jdbc:postgresql://172.17.0.1:5432/fact_dev (PostgreSQL 13.11)
2024-09-06 16:40:23.068 INFO 1 --- [ main] o.f.core.internal.command.DbValidate : Successfully validated 337 migrations (execution time 00:00.459s)
2024-09-06 16:40:23.114 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Current version of schema "public": 3.4.199
2024-09-06 16:40:23.119 INFO 1 --- [ main] o.f.core.internal.command.DbMigrate : Schema "public" is up to date. No migration necessary.
2024-09-06 16:40:23.371 INFO 1 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
Flyway is not applying the new migrations and continues to show that the schema is already up-to-date.
How can I get Flyway to apply migrations up to version 3.4.258? Are there any settings or parameters that might be affecting this behavior?
Hi everyone,
I'm encountering an issue with Flyway when managing migrations in PostgreSQL. Here's the situation:
In the Flyway logs, it shows that the current schema version is
"public": 3.4.199, and it reports that the schema is up-to-date and no migration is necessary:I have 369 migrations in the folders, with the latest migration version being 3.4.258.
Flyway is not applying the new migrations and continues to show that the schema is already up-to-date.
How can I get Flyway to apply migrations up to version 3.4.258? Are there any settings or parameters that might be affecting this behavior?