Module terminus_store::layer

Logic for working with layers.

Databases in terminus-store are stacks of layers. The first layer in such a stack is a base layer, which contains an intial data set. On top of that, each layer stores additions and removals.

Re-exports

• pub use id_map::*;

Modules

• base
  Base layer implementation.
• base_merge
• builder
• child
  Child layer implementation
• id_map
• rollup

Structs

• BaseLayer
  A base layer.
• BaseLayerFileBuilder
  A builder for a base layer.
• BaseLayerFileBuilderPhase2
  Second phase of base layer building.
• BaseTripleStream
• ChildLayer
  A child layer.
• ChildLayerFileBuilder
  A builder for a child layer.
• ChildLayerFileBuilderPhase2
  Second phase of child layer building.
• ChildTripleStream
• IdTriple
  A triple, stored as numerical ids.
• InternalLayerTripleObjectIterator
• InternalLayerTriplePredicateIterator
• InternalLayerTripleSubjectIterator
• InternalTripleObjectIterator
• InternalTriplePredicateIterator
• InternalTripleStackIterator
• InternalTripleSubjectIterator
• LayerCounts
• OptInternalLayerTripleObjectIterator
• OptInternalLayerTriplePredicateIterator
• OptInternalLayerTripleSubjectIterator
• PartiallyResolvedTriple
  A triple where the subject, predicate and object can all either be fully resolved to an id, or unresolved.
• RollupLayer
• SimpleLayerBuilder
  A layer builder
• ValueTriple
  A triple stored as strings.

Enums

• InternalLayer
• LayerStackError
• ObjectType
  The type of an object in a triple.
• PossiblyResolved
  Either a resolved id or an unresolved inner type.
• TripleChange

Traits

• Layer
  A layer containing dictionary entries and triples.
• LayerBuilder
  A layer builder trait with no generic typing.

Functions

• open_base_triple_stream
• open_child_triple_stream