Engine Room Mechanics
The Unibase Data Dictionary
Deterministic DNA & Direct-Execution Blueprints
Field-Level Primitives: The Data Atoms
In Unibase, data types are not just storage containers; they are behavioral definitions. Every field in the dict.dat is defined with specific width and type parameters that the kernel enforces at the hardware level.
| Type Code | Definition | Mechanical Advantage |
|---|---|---|
AN |
Alphanumeric | Variable-length string storage with $O(1)$ indexing. |
N0 - N4 |
Numeric (Decimal) | Fixed-point math precision managed by the Equation Solver. |
PX |
Product Number | Specific optimized format for high-velocity inventory lookups. |
DT / TM |
Date & Time | Internal Julian conversion for instant interval calculations. |
Virtual Intelligence: Non-Procedural Fields
One of the most powerful features of the Unibase Engine is Virtual Fields. These are fields that do not exist as stored data but are calculated in real-time based on equations defined in the dictionary.
The Hardened Conscience of Calculations
If Total_Price is a virtual field defined as Qty * Unit_Price, Unibase ensures that any change to Qty or Unit_Price propagates the new truth instantly. The developer never writes an “update” function; the DNA handles it.
The Relational Syntax: *, +, -, =
The Dictionary uses a specific “Shorthand of Power” to define how tables interact without the overhead of SQL Join statements.
Designates a Master-Detail relationship. Deleting a customer record automatically and safely purges all associated orders, preventing “ghost data” or logic leaks.
A Persistent Peer relationship. Ensures that both tables remain synchronized in real-time, regardless of which side of the relationship is updated.
The First-Record Anchor. Instantly resolves an association to the first chronological or indexed entry in a linked table.
The Last-Record Anchor. Vital for inventory and balance tracking where the current state is always the most recent entry.
Modular DNA: Scaling the Unit of One
A single dict.dat can become massive. Unibase handles this via **Includes**. An architect can break the dictionary into logical modules (e.g., Finance, Logistics, Inventory) while the kernel treats them as a single, unified consciousness.
- Hot-Swapping: Use ubreload to update a module’s DNA without stopping the execution of the other modules.
- Memory Profiling: The kernel allocates memory based on the dictionary definitions, ensuring no “bloat” exists in the production runtime.
