Schema-agnostic Staged Changesets with stage.substituteSchemasTL;DR SQLcl Projects 26.1.0 supports a stage.substituteSchemas flag that makes staged artifacts schema-agnostic by replacing schema references with Liquibase property substitution (e.g., hr → ${hr}). 1Apr 3 · 6 min readdanmcghan.hashnode.dev
The Problems with Liquibase Rollback — and What to Do InsteadA common question we get: why doesn’t SQLcl Projects support Liquibase rollback? At first glance, Liquibase’s rollback feature seems like a great safety net. Not only can it evolve your schema forward, it promises to take you backward if something go...May 31, 2025 · 4 min readdanmcghan.hashnode.dev
Feature Branches vs. End-of-Release Branches: Which Approach Works Best?The Question Someone recently asked me: What's the possibility/risk of just using one dev branch and multiple developers working in there, then just merge to main when a release/artifact is generated? Good Practice? Bad Practice? Thoughts? Risky Bu...Feb 17, 2025 · 3 min readdanmcghan.hashnode.dev
Upgrading SQLcl When Using SQLcl ProjectsKeeping your development tools up to date is essential for smooth collaboration and to take advantage of the latest features and fixes. When working with SQLcl Projects, upgrading SQLcl requires a structured approach to minimize disruption and ensure...1TFeb 14, 2025 · 3 min readdanmcghan.hashnode.dev
Admin vs. App User Installation: Choosing the Right Path for Secure, Efficient DeploymentsChoosing the right deployment approach is essential when deploying changes to Oracle Database and APEX applications. One key decision involves selecting between an admin (privileged) user installation and an app (object owner) user installation. Each...1SJan 4, 2025 · 5 min readdanmcghan.hashnode.dev
