The Pre-Processor Macro Engine Mechanics
The Data Dictionary Macro Facility inside the Unibase backend handles in-compiler template automation. Rather than resolving layout constraints or record lookups at runtime—which causes database latency—the macro facility intercepts the compilation pipeline. It expands reusable schema blueprints and field parameters directly into absolute machine-readable source blocks before execution. This decoupled model ensures that database engines enforce field validations natively at maximum CPU throughput.
Core Data Dictionary Macro Directives
The backend pre-processor tracks explicit, dollar-prefixed keywords to structure macro code blocks, pass argument strings, and isolate expansion scopes. The following literal controls must be applied exactly:
| Macro Command Token | Argument Allocation Bounds | Pre-Processor Execution Trait & Expansion Output |
|---|---|---|
$MACRO |
Name(Param1, Param2) |
Declares a named, isolated pre-compiler block and registers its input parameter signatures inside the compilation symbol index. |
$ENDMACRO |
None | Terminates the parsing loop for the active macro definition block, locking down the interior code blueprint against leakage. |
%ParamName |
Literal Text String | Acts as an inline parameter replacement marker. The pre-processor automatically swaps this with the passed variable during compilation loops. |
$INCLUDE |
"filename.mac" |
Suspends processing of the main file to inline parse and append the contents of an external macro library source directly into the compiler track. |
Compile-Time Macro Generation Syntax
The code blueprint below demonstrates how to declare an validation macro rule within a data definition module, load helper directives, and invoke the injection engine cleanly:
$INCLUDE “financial_bounds.mac”
// 2. Define an inside-compiler structural constraint template rule
$MACRO GenerateAuditValidation(FieldName, MinimumValue, ErrorLogCode)
if (%FieldName < %MinimumValue) then
execute log_security_breach(%ErrorLogCode, “%FieldName value boundary clip outside bounds”);
reject_db_transaction;
end if
$ENDMACRO
// 3. Invoke the expansion facility within the transactional ledger schema compilation track
FIELD: commercial_wire_amount
TYPE: DECIMAL_64
VALIDATION_LOOP: GenerateAuditValidation(commercial_wire_amount, 10000, “ERR_WIRE_CAP_OOB”)
Engine Processing Notice: Parameters prefixed with the percentage token (%) evaluate purely as structural string replacements inside the macro shell. Always match your macro arguments to the target Data Dictionary field names to guarantee compilation success.
Defensible Backend Performance Value
Standardizing system data pipelines around the compiled Unibase Macro Facility yields clear, defensible platform valuation vectors:
| Zero Runtime Latency | Because macro rules expand completely before execution, complex field logic runs natively at compiled speeds, bypassing interpreting query layer steps. |
| Centralized Policy Locking | Enables infrastructure teams to define security checks inside isolated, read-only .mac include assets, shielding your logic from developer configuration drift. |
| Hardened Schema Immunity | Enforces global security parameters and data formatting compliance directly into structural binary trees, blocking data corruption at the compiler boundary. |
