Feature: current_state
Table of Contents
This page is one authored MASD feature in ORE Studio Variability Model § "Projection configuration: how an existing artefact family is shaped". Any profile that fixes this feature's value links here rather than restating its effect.
1. Identity
| Field | Value |
|---|---|
| Literal name | :current_state: |
| Bundle | ores.sql.schema |
| Type | bool |
| Default | false |
2. Effect
The table holds one row per key and no history. The value is read from the
model's * SQL ** Flags drawer and selects the current-state DDL in place of
the bi-temporal shape: no version column, no valid_from=/=valid_to pair,
no GIST exclusion, no insert trigger doing version management and no delete
rule that soft-closes a row.
The rest of the surface follows the same flag. A current-state entity has no versions sub-resource, so no version records, no version operations and no version subscription are generated. That covers the NATS handler and its registrar, the C++ protocol header and the TypeScript twin. An ordinary entity keeps every one of them.
3. Structural consequence
The table shape, and through it the entity struct: the audit tail and the temporal columns are absent, so the generated sqlgen entity carries neither. A current-state model and a bi-temporal model of the same columns therefore do not produce the same table.
4. Used by
5. See also
- read_only — the wire surface this feature is usually paired with.
- ORE Studio Variability Model — the bundle this feature belongs to.