Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Which version and edition of Flyway are you using?
6.0.4 - 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)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Which database are you using (type & version)?
Azure MySQL 5.7, not 5.6 as the error says. See this note in Azure:
NOTE: In the service, a gateway is used to redirect the connections to server instances. After the connection is established, the MySQL client displays the version of MySQL set in the gateway, not the actual version running on your MySQL server instance. To determine the version of your MySQL server instance, use the SELECT VERSION(); command at the MySQL prompt.
Which operating system are you using?
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
Ran the flyway maven plugin to migrate an Azure database for the first time:
What did you expect to see?
The database tables created.
What did you see instead?
[ERROR] Failed to execute goal org.flywaydb:flyway-maven-plugin:6.0.4:migrate (default-cli) on project initializer: org.flywaydb.core.internal.license.FlywayEditionUpgradeRequiredException: Flyway Enterprise Edition or MySQL upgrade required: MySQL 5.6 is no longer supported by Flyway Community Edition, but still supported by Flyway Enterprise Edition. -> [Help 1]
Looks like this is a bug within the MySQL Azure service itself:
I don't think we can do anything about it unfortunately. We'll have to wait for Microsoft to fix the issue on their end.
Essentially we can spot the case where the JDBC metadata and result of
@Matonen I couldn't reproduce this odd result (