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
MariaDB not recognized with MariaDB JDBC driver 2.4.0 #2289
Comments
Interesting. Would using a |
I tried but it was still failing, the error was different tho I think. Additionally there was that warning about using mariaDB driver on mysql. |
@axelfontaine Any hope we might get this issue rolled into a point release? Seems like it is already fixed in |
@tomas-silhavy Thanks for reporting and @pismy thanks for investigating. This has now been implemented along with official support for MariaDB 10.4 (#2300). |
It'd be create to get this fix in 5.2.x as well as I'm also dead in a water with flyway on this driver issue. |
@jvalkeal Perhaps https://flywaydb.org/blog/flyway-6.0.0-beta will work for you? My solution was to do a compile of master and throw it in a local maven mirror while waiting for an official release. |
No, we really can't go down that route as this is for spring libraries build on spring boot and we can't release with unsupported dependencies. |
For a workaround for those who can't upgrade to 6.0.0-beta just yet, see #2339 (comment) |
Which version and edition of Flyway are you using?
5.2.4
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)
maven plugin 5.2.4
Which database are you using (type & version)?
MariaDB 10.2
breaks: mariadb-java-client: 2.4.0 -> databaseProductName = MariaDB 10.2
works: mariadb-java-client: 2.3.0 -> databaseProductName = MySQL 10.2
Which operating system are you using?
ubuntu
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.)
just running normal mvn compile
What did you expect to see?
build successful...
What did you see instead?
The text was updated successfully, but these errors were encountered: