-schemas causing schema version `null`

Which version and edition of Flyway are you using?

docker flyway/flyway 7.5.0

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)

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

CLI

Which database are you using? (Type & version)

postgres 9.5

Which operating system are you using?

docker on 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)

There is not configuration file present and no jars, this is a plain usage of the docker image together with a postgres database.

command (inside the docker container): flyway -user=... -password=... -schemas=my_schema -url=jdbc:postgresql://db:5432/postgres migrate

SQL on /flyway/sql/V1__Initial.sql (mounted):

CREATE TABLE my_schema.table (
    my_test INTEGER NOT NULL,
    ... 
)

What did you expect to see?

The migration be applied.

What did you see instead?

Creating schema "my_schema" ...
Creating Schema History table "my_schema"."flyway_schema_history" ...
Current version of schema "my_schema": null
Schema "my_schema" is up to data. No migration necessary.

When -schema=my_schema is not passed (and CREATE TABLE does not include it) the migration is applied correctly.

[jorgecarleitao]

Thanks a lot for your help, “-X” really helped solving the problem. The sql directory was incorrectly mounted, which caused the sql files to be empty. Funny that it did not said that there were no files, but that is beyond the point.

Thanks a lot both for your help.

[teotwaki]

Hi @jorgecarleitao,

Did you extract the DDL from the existing database? As far as I understand, Flyway can’t apply new changes if it doesn’t have a starting point.

https://flywaydb.org/documentation/learnmore/existing