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
Flyway 6.0.1 parser bug #2522
Comments
@sladis Thanks for reporting this. Any chance you can share the entire migration script (with any sensitive bits redacted) so that we can attempt a reproduction? |
|
I'm not sure how to put sql in there, tried as comment, I hope it will be usefull. |
@sladis I've managed to reproduce the issue, which doesn't seem to be related to the presence of Czech characters, but with the presence of two or more comment lines before a SQL*Plus For example, the following also reproduces the problem: /* Multi-line comment */
-- Inline comment
SET DEFINE OFF |
Good job finding the issue,thanks! Is it flyway bug and will it be fixed? |
Yes, the fix will ship in the next release. |
@sladis Thanks again for reporting and for your help with reproducing this! |
Which version and edition of Flyway are you using?
6.0.1. Enterprise
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)
Cmd
Which database are you using (type & version)?
Oracle12
Which operating system are you using?
Unix
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.)
First 3 lines of sql script is multiline comment containing characters č,í,ú
Like:
What did you expect to see?
Run sql script without errors
What did you see instead?
ERROR: Unable to parse statement in V1_script.sql at line 1 col 1: flyway parser bug: token text is null (COMMENT -> 2:1)
The text was updated successfully, but these errors were encountered: