I just got caught by this by surprise as well. I can work around it easily, but it'd be nice if flyway was either always creating all missing schemas or not create any schemas at all (requiring this to be done in the migration files manually).
Right now I always need to do this in my migration files when adding a new schema:
CREATESCHEMAIF NOT EXISTS my_new_schema;
But this leads to the following warning when setting up a new machine:
Care to elaborate on that a bit? For MySQL, I find it difficult to believe it is intended to try and fail creation of the history table ten(!) times in a row, if the containing schema doesn't exist but one of the the others does.
Also what is the plan of resolving this old issue? The workaround for injecting the schema for the history table beforehand isn't that nice either.