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

Flyway parsing bug: unable to decrease block depth below 0 in version 6.3.0 #2715

rafael-trevisan opened this issue Mar 10, 2020 · 2 comments


Copy link

@rafael-trevisan rafael-trevisan commented Mar 10, 2020

Which version and edition of Flyway are you using?

6.3.0 Pro

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)
In v6.2.4 flyway was removing the ";" from my package spec. I upgraded to 6.3.0 and now it raises an error on the line that has the final ";"

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


Which database are you using (type & version)?

Oracle 18

Which operating system are you using?


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.)
In v6.2.4 I was having an issue where Flyway was removing the last ";" from my package spec causing them to be invalid. I upgraded to 6.3.0 hoping the issue could go away but now Flyway raises an exception on the exact line that has the last ";"

Example of the code:

create or replace package package_a authid current_user as

  gc_a constant varchar2(1024)   := 'bla';
  g_b number;
  procedure x (
    some_param number
end package_a;
Copy link

@rafael-trevisan rafael-trevisan commented Mar 10, 2020

I downgraded to version 6.2.0 and the issue is gone.

@Lyeeedar Lyeeedar added this to the Flyway 6.3.1 milestone Mar 10, 2020
@Lyeeedar Lyeeedar self-assigned this Mar 10, 2020
Copy link

@Lyeeedar Lyeeedar commented Mar 11, 2020

Fixed in c229730

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