-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
EndDelimiter "$$" cannot be correctly parsed in SQL of a change set after upgrading Liquibase to 4.29.2 #6403
Comments
Hi @wangweiao, I have two questions in order to better understand this issue:
Thank you, |
Hi @tati-qalified ,
Best regards, |
@wangweiao it seems that Liquibase is interpreting the For 4.27.0:
For 4.28.0 through 4.29.2:
So now it's separating the "create" sentence from the function definition. This happens since Liquibase version 4.28.0. We'll be looking into this. If you'd be willing to submit a PR to propose a fix, feel free to do so! Thank you, |
Hi Wang (@wangweiao), If I'm not wrong this is working as expected. Recently, some endDelimiter issues have been fixed and this reported case seems to be behaving correctly. If we use Statement 1: create function foo() returns trigger AS Statement 2: begin
...
end; Statement 3: language plpgsql;
create trigger
...
execute procedure foo(); Then execution of statement one is not a valid Thanks, |
Search first
Description
We are deploying SQL and PL/pgSQL scripts on an PostgreSQL Database via Liquibase. We use "$$" as endDelimiter in our code.
Since 4.29.2 this is some kind of broken. Now endDelimiter "$$" cannot be correctly parsed in SQL of a change set after upgrading Liquibase.
Steps To Reproduce
Error caused:
Expected/Desired Behavior
"$$" should be parsed as endDelimiter as before.
Liquibase Version
4.29.2
Database Vendor & Version
PostgreSQL 42.6.1
Liquibase Integration
No response
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: