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

6.2.3 breaks our migrations MYSQL. #2675

Closed
ValdemarGr opened this issue Feb 17, 2020 · 0 comments
Closed

6.2.3 breaks our migrations MYSQL. #2675

ValdemarGr opened this issue Feb 17, 2020 · 0 comments

Comments

@ValdemarGr
Copy link

@ValdemarGr ValdemarGr commented Feb 17, 2020

Which version and edition of Flyway are you using?

6.2.3

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)

CLI MySQL driver.

Which database are you using (type & version)?

MySQL 5.7 (dockerfile)

Which operating system are you using?

docker deb

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.)

CREATE DATABASE IF NOT EXISTS DB_NAME;
What did you expect to see?

The database created.

What did you see instead?
ERROR: Unable to parse statement in /flyway/sql/DB_NAME/V1971.01.09.02.18.00__DB_NAME_initial_creation.sql at line 1 col 1: Incomplete statement at line 1 col 1: CREATE DATABASE IF NOT EXISTS DB_NAME;

This is the very first migration we run, I have tried with an earlier vrsion (flyway/flyway:6.2.1), and it works fine.

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

No branches or pull requests

3 participants