Declarative dataflow infrastructure
This crate contains types, traits, and logic for assembling differential dataflow computations from declaratively specified programs, without any additional compilation.
Binding language, mainly for use in Hector-powered plans.
Logic for working with attributes under a shared timestamp semantics.
Types and traits for implementing query plans.
Server logic for driving the library via commands.
Types and operators to feed outputs into external systems.
Types and operators to work with external data sources.
Various timestamp implementations.
Various indices over a collection of (K, V) pairs, required to participate in delta-join pipelines.
A collection and variable bindings.
An entity, attribute, value triple.
A client-facing, non-exceptional error.
CollectionIndex that was imported into a scope.
A named relation.
A wrapper around a vector of ShutdownButton's. Ensures they will be pressed on dropping the handle.
Transaction data. Conceptually a pair (Datom, diff) but it's kept intentionally flat to be more directly compatible with Datomic.
Attribute indices can have various operations applied to them, based on their semantics.
Possible timestamp types.
Possible data values.
Returns a deduplicates list of all rules used in the definition of the specified names. Includes the specified names.
Takes a query plan and turns it into a differential dataflow.
Helper function to create a query plan. The resulting query will provide values for the requested target variables, under the constraints expressed by the bindings provided.
A unique attribute identifier.
A unique entity identifier.
Alias for a
A handle to an arranged relation.
A (tuple, time, diff) triple, as sent back to clients.
A trace of values indexed by self.
A trace of (K, V) pairs indexed by key.