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

Migration files with hard spaces don't work anymore #2446

Closed
AigleeK opened this issue Jul 25, 2019 · 4 comments

Comments

@AigleeK
Copy link

commented Jul 25, 2019

Which version and edition of Flyway are you using?

Flyway 6 Beta Nightly Snapshot

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

Command-Line

Which database are you using (type & version)?

SQL Server 2017

Which operating system are you using?

Windows 10

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.)
Any SQL statement using a hard space instead of a regular space causes the issue

What did you expect to see?

Migration should have worked. It works in Flyway 5

What did you see instead?

ERROR: Unable to parse statement in ...\Migrations\V10.12.0_201906211538__File_Name.sql at line 1 col 1: Unknown char   encountered on line 1 at column 3

@juliahayward

This comment has been minimized.

Copy link
Member

commented Jul 25, 2019

Can you share the exact migration .sql file please? Or failing that, a minimal reproduction?

@AigleeK

This comment has been minimized.

Copy link
Author

commented Jul 25, 2019

@juliahayward

This comment has been minimized.

Copy link
Member

commented Jul 25, 2019

Great, thankyou!

juliahayward added a commit to flyway/flywaydb.org that referenced this issue Jul 26, 2019

@juliahayward juliahayward added this to the Flyway 6.0.0 milestone Jul 26, 2019

@juliahayward

This comment has been minimized.

Copy link
Member

commented Jul 26, 2019

Thankyou very much for the report! A fix is now pushed and will be rolled up into the v6.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.