Hi,
I'm currently working with SQLcl on a project that involves large PL/SQL packages, and I'm looking for an efficient workflow to manage them—especially in terms of version control and code review.
At the moment, every change results in the entire package body being copied to the dist folder. When I set softObjectIsolation to release, it seems the package is only copied once per release, which helps reduce redundancy. However, this setup isn't ideal for code reviews, as reviewers still need to inspect diffs in the src folder and there's no meaningful diff in the dist folder (which actually gets deployed).
Liquibase offers a runOnChange=true option that automatically detects changes and executes the changeset accordingly. Is there a specific reason why this mechanism isn't supported or commonly used for soft objects in SQLcl? It would be much more convenient to maintain packages and similar objects in a single folder.
Do you have any recommended Git workflows for handling large PL/SQL packages—particularly regarding code reviews and release management?
Thanks in advance for your insights!
Best regards,
Markus