We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems that the procedure in ora:createTrigger does not preserve line breaks when executing the code.
If the code contains like
stmt1 --- some comment stmt2
are compiled as stmt1 --- some comment stmt2
so it is in error when checking in sql developer.
Would it be possible to preserve the line break?
When migrating existing databases to liquibase it is a lot more straight forward if it would.
┆Issue is synchronized with this Jira Bug by Unito
The text was updated successfully, but these errors were encountered:
https://github.com/liquibase/liquibase-oracle/issues/15
5320541
adding alternative to "procedure" attribute for the create trigger a procedureNode xml node.
Merge pull request #28 from iszilagyigit/master
127fabf
#15
No branches or pull requests
It seems that the procedure in ora:createTrigger does not preserve line breaks when executing the code.
If the code contains like
stmt1 --- some comment
stmt2
are compiled as
stmt1 --- some comment stmt2
so it is in error when checking in sql developer.
Would it be possible to preserve the line break?
When migrating existing databases to liquibase it is a lot more straight forward if it would.
┆Issue is synchronized with this Jira Bug by Unito
The text was updated successfully, but these errors were encountered: