gnitz-store 0.1.0

The Z-set store of the gnitz database: LSM storage, relation registry and read executor
docs.rs failed to build gnitz-store-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

Gnitz

Gnitz is a SQL database. What makes it different from most other SQL databases is that VIEWs are all materialized and incrementally updated, meaning: They never go stale, and they are updated efficiently – the cost to update a VIEW is always proportional to the size of the changed data, regardless of how much existing data there is. It intentionally restricts SELECT statements to the bare minimum so that queries are always fast, no footguns. Gnitz spills these VIEWs to disk, so it trades disk-space for latency.

A Gnitz guarantees efficient VIEW updates by implementing the DBSP (Differential Dataflow) formal model, treating all data as Z-Sets – multisets where every record has an associated integer weight, enabling algebraic coalescing of updates.