Which version and edition of Flyway are you using?

flyway-core 9.22.3 community edition

If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)

yes

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

Java API

Which database are you using? (Type & version)

IBM DB2

Which operating system are you using?

Linux

What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)

I'm sharing one schema with multiple flyway migrations. Each migration maintains an independent set of tables. Everything is working and each flyway migration has it's own flyway history table. Now I'm trying to add baselining to the migrations to speed up the initialization of new databases.

I have this simple scenario:

V1.0__CreateTable.sql  <- initial table
V1.1__AddFirstName.sql <- add new column
B2.0__Baseline.sql <- cumulation of V1.0 and V1.1
V2.1__AddEmail.sql <- add another column

The schema, where the migration is running is not empty, so other tables are already existing because of previously running migrations.

My flyway is configured like this:

Flyway.configure()
				.dataSource(dataSource)
				.locations(scriptsLocation)
				.schemas(migration.getSchema())
				.baselineVersion("0")
				.baselineOnMigrate(true)
				.table(migration.getFlywayTable())
				.load();

The scripts are correctly parsed:

[de.afb.core.flyway.MigrationController] State: BELOW_BASELINE Version: 1.0 Description: CreateTable
[de.afb.core.flyway.MigrationController] State: BELOW_BASELINE Version: 1.1 Description: AddFirstName
[de.auskenfuchs.core.flyway.MigrationController] State: PENDING Version: 2.0 Description: Baseline2
[de.auskennfuchs.core.flyway.MigrationController] State: PENDING Version: 2.1 Description: AddEmail

So Flyway correctly identifies V1.0 and V1.1 as below the newest baseline. But still these scripts are executed and B2.0 is ignored completely.
When I'm running the same Migration on an empty schema everything works like expected, B2.0 and V2.1 are execucted and V1.x are ignored. In every case I'm providing the baselineVersion as 0.

What did you expect to see?

I would expect that also on not empty schemas the baseline is correctly used.

What did you see instead?

The baseline version is ignored on non empty schemas. Even when I'm setting the baselineVersion to 2 or 1.9 the baseline script is never executed.

I assume there were some decisions that only empty schemas can guarantee the proper baseline with flyway, but in some scenarios this may not apply. It would be good to have an option that the baseline is still applied, as long as the flyway history table doesn't exist.