You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does Liquibase Support .pks/.pkg/.pkb for migration like .sql? When renaming the .pks/.pkb to .sql then only packages executes not if given in .pks/.pkg extensions.
.pks/.pkg/.pkb are common file extensions for PL/SQL-Packages.
Most GUIs need the suffixes to distinguish between SQL (or PL/SQL) scripts and packages, because the latter are opened in a special editor.
Renaming the package files to .sql would be very inconvenient for the developer.
If Liquibase treated .pks/.pkg/.pkb files like .sql files it would be very helpful.
It would be very useful to be able to use some regular expression in the <includeAll> tag so that only filenames we are interested in are picked during the migration, rather than just using all default .sql, .xml, .yaml and .json files.
Currently, it is only possible to implement a custom filter class in Java, but due to the use of Liquibase in SQLcl, it is not possible to do it.
Hi ,
Does Liquibase Support .pks/.pkg/.pkb for migration like .sql? When renaming the .pks/.pkb to .sql then only packages executes not if given in .pks/.pkg extensions.
┆Issue is synchronized with this Jira Bug by Unito
The text was updated successfully, but these errors were encountered: