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

Whitespace after "/" delimiter causes migration to fail. #2560

jeroenroosen opened this issue Nov 12, 2019 · 1 comment

Whitespace after "/" delimiter causes migration to fail. #2560

jeroenroosen opened this issue Nov 12, 2019 · 1 comment


Copy link

@jeroenroosen jeroenroosen commented Nov 12, 2019

Which version and edition of Flyway are you using?

6.0.8 community

If this is not the latest version, can you reproduce the issue with the latest one as well?

(Works in 4.2, 6.0.7)

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


Which database are you using (type & version)?

Oracle 12

Which operating system are you using?


What did you do?

SQL file that ends with "/ ": a space followed by a whitespace, then migrate.

What did you expect to see?

In 4.2 this did not cause any issues, migrate would succeed.

What did you see instead?
SQL State  : 65000
Error Code : 6550
Message    : ORA-06550: line 6, column 1:
PLS-00103: Encountered the symbol "/" The symbol "/" was ignored.

I could find #2530 and #2493, it seems that our problem is somewhere in between because we have a trailing whitespace after the / which didn't cause any trouble in Flyway 4 and before.

Copy link

@alextercete alextercete commented Nov 12, 2019

@jeroenroosen Thanks for reporting this.

As you have noticed, we've been chasing / issues in Flyway 6 and Oracle for a little while. Hopefully, there aren't many more edge cases to consider after this one.

@alextercete alextercete removed this from the Flyway 6.1.0 milestone Nov 26, 2019
@alextercete alextercete added this to the Flyway 6.1.1 milestone Nov 26, 2019
dohrayme pushed a commit to dohrayme/flyway that referenced this issue Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants