Oracle & APEX developer
Whenever I run into something interesting, I try to turn it into an article here. Please take a look.
-
APEXlang vs SQL Deployment: The Network Path Determines the Winner
APEXlang and SQL imports trade database work for network trips. Tests from a local VM, across a VPN, and near an OCI database show when each is faster.
-
SQLcl Project 26.2.2: Two APEXlang Directory Structures, One Migration Blocker
SQLcl 26.2.2 adds useful APEXlang deployment support, but its two source layouts preserve old export defects, introduce new regressions, and remove a critical workaround.
-
Upgrading Oracle APEX and SQLcl to 26.1 in a Busy Development Environment
A real-world architecture for adopting APEX 26.1, SQLcl 26.1, SQLcl Project, and APEXlang while development and production support continue.
-
Maintaining Different SQLcl Versions for Different Repositories and Folders
A PROMPT_COMMAND hook in ~/.bashrc that switches the SQLcl version on your PATH automatically whenever you change directory — useful during upgrades and when working across projects on different SQLcl releases.
-
Substitution Variables in SQLcl Project: An Underused Liquibase Feature
Liquibase property substitution lets you inject values from a properties file or OS environment variables into any changeset. Available since the first SQLcl Project release (24.3 onward) but absent from the official docs — which explains why it is so often overlooked.
-
SQLcl Project Aliases: A Practical Toolkit for Daily Development
A practical collection of SQLcl aliases for safer SQLcl Project exports, deployments, Liquibase operations, and APEXlang development.
-
Native Boolean Columns in Oracle APEX 26.1 and APEXlang
How to keep native Oracle Boolean values correctly typed through APEX sources, session state, controls, and APEXlang validation.
-
Merging APEX Working Copies with APEXlang
A practical workflow for combining parallel Oracle APEX development by using working copies, APEXlang, and SQLcl together.