Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New configuration parameter flyway.defaultSchema #2576

juliahayward opened this issue Nov 25, 2019 · 2 comments

New configuration parameter flyway.defaultSchema #2576

juliahayward opened this issue Nov 25, 2019 · 2 comments


Copy link

@juliahayward juliahayward commented Nov 25, 2019

At the moment the config parameter flyway.schemas is overloaded:

  • it provides a list of schemas to be created and to be cleaned
  • the first of the list is taken to be the default schema for the database connection (where the database supports the concept of a default schema) and the location of the schema history table

We will introduce a new configuration parameter flyway.defaultSchema which will take over the second of those two functions. Initially, in Flyway 6.1 and subsequent 6.x.x releases, if defaultSchema is not specified then we default back to the current behaviour.

@juliahayward juliahayward added this to the Flyway 6.1.0 milestone Nov 25, 2019
Copy link
Member Author

@juliahayward juliahayward commented Nov 26, 2019

Implemented in 6.1.0

Copy link

@mlanglet mlanglet commented Feb 3, 2020

Hi. We're using spring boot 2.2.2 with flyway 6.1.4 and specify spring.flyway.schemas=my_schema and I saw this flyway warning being printed about the defaultSchema property on startup. I tried adding spring.flyway.defaultSchema=my_schema to suppress it but the warning is still showing up. Is this something you peeps at Redgate can fix or is it something spring boot needs to get up to speed with and propagate the property properly?

Also I couldn't find this property documented at

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants