Elaborating more on my question, is there a recommended workflow for versioning code / apps / schema changes using the mix of tools, SqlCl as a driver with embedded LiquiBase integrated with GIT, where a single activity would generate the change log into liquibase for migration but also produces the necessary git compliant (standardized) export of the "code"? I liked @martindsouza episode on a prescriptive versioning workflow and I've been noticing that SqlCl integrates most of the pieces very nicely. so instead of a shell script driving sql and then invoking git, is there any way we could do the same (hopefully even nicer) in sqlcl alone ?
Thnx guys!
Elaborating more on my question, is there a recommended workflow for versioning code / apps / schema changes using the mix of tools, SqlCl as a driver with embedded LiquiBase integrated with GIT, where a single activity would generate the change log into liquibase for migration but also produces the necessary git compliant (standardized) export of the "code"?
I liked @martindsouza episode on a prescriptive versioning workflow and I've been noticing that SqlCl integrates most of the pieces very nicely.
so instead of a shell script driving sql and then invoking git, is there any way we could do the same (hopefully even nicer) in sqlcl alone ?