Module impl_ephemeral 

Ephemeral store materialization (PRD #1785, issue #1786).

The red binary can take a local CSV/TSV file plus an RQL query, materialize the file as a row table inside a throwaway in-memory embedded store, run the query, and discard the store — no server, no pre-existing store, nothing durable created.

This module is the CSV/TSV tracer: the skeleton every other ephemeral slice (JSON/documents, multi-file, writes/--save) extends. It rides the existing CSV import path (the shared CsvImporter) so the file becomes a real row table with header-derived columns and inferred types.

Loaded collections are named by their sanitized file stems and by positional file aliases. A single loaded file also gets the legacy alias POSITIONAL_ALIAS (t). Multi-file loads get t1, t2, … in argument order. When multiple stems sanitize to the same name, the first keeps the base name and later collisions receive _2, _3, … suffixes in argument order; the positional aliases are therefore the guaranteed-unambiguous handles.

Structs

EphemeralTable

Outcome of materializing a data file into the ephemeral store.

Enums

EphemeralError

A didactic error explaining why a file could not be materialized.

Constants

POSITIONAL_ALIAS

Positional alias for the single loaded file: SELECT … FROM t.

Functions

sanitize_stem

Sanitize a file stem into a safe collection identifier.