Branching & history
Change Detection / Diff
Diffing two read targets uses a three-level algorithm:
Diffing two read targets uses a three-level algorithm:
- Manifest diff: skip sub-tables whose
(table_version, table_branch)is unchanged. - Lineage check:
- Same branch lineage → fast path: use the per-row
_row_last_updated_at_versioncolumn to classify Insert/Update/Delete. - Different lineages → ID-based streaming comparison.
- Same branch lineage → fast path: use the per-row
- Row-level diff: streaming, no full materialization.
Public API
diff_between(from: ReadTarget, to: ReadTarget, filter: Option<ChangeFilter>) -> ChangeSetdiff_commits(from_commit_id, to_commit_id, filter)— cross-branch safe.
Types
ChangeOp: Insert | Update | Delete
EntityKind: Node | Edge
EntityChange { table_key, kind, type_name, id, op, manifest_version, endpoints?: {src, dst} }
ChangeFilter { kinds?, type_names?, ops? }
ChangeSet { from_version, to_version, branch?, changes[], stats }Transactions in OmniGraph
OmniGraph does not have BEGIN / COMMIT / ROLLBACK. Branches do that job. This page explains the model, when to use which primitive, and shows worked examples...
Maintenance: Optimize, Repair & Cleanup
Addressing. optimize, repair, and cleanup are direct (storage-native) CLI commands: they run with direct storage access against a positional file:///s3:// UR...