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

Does Liquibase Support pks/pkb for migration? #33

Open
Barathwaja opened this issue May 13, 2019 · 3 comments
Open

Does Liquibase Support pks/pkb for migration? #33

Barathwaja opened this issue May 13, 2019 · 3 comments

Comments

@Barathwaja
Copy link

Barathwaja commented May 13, 2019

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

@Barathwaja
Copy link
Author

@nvoxland Can you help me out on this one? Thanks

@apexbine
Copy link

.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.

@kucerajo
Copy link

kucerajo commented Apr 8, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants