Expose flyway.schemas as default placeholder #3564
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background:
I run on oracle with multiple complex schemas an heavy use of packages.
It can happen that packages have failures but anyhow get migrated succesfully as no ORA error is thrown.
In addition it can happen that packages are on failure, but after triggering re-compilation they work.
In order to solve that, I have a afterMigrate.sql script, which recompiles first invalid objects and then verifies if all are in valid state.
This script needs the schema names in order to look only to relevant schemas. I want to make this script re-usable and therefor use the information from flyway.schemas from configuration. I would use this info to split it and do the checks per schema accordingly. Currently I can only do it with the defaultSchema or hardcode all schema names in the script I want to avoid.
Please have a look and feedback if I have missed something or need to further do something.