Namespace for collecting a suite of tools for administrative tasks on eva
databases, such as migration and backup.

Entry point for Eva Administrative CLI tooling

Provides a generic protocol for traversing hierarchically linked data,
and implementations of that protocol against stored Eva objects

Provides a basic implementation for migration handled through a flowgraph

Supporting implementation of functions
in eva.Util class

Abstraction point for modifying built in database functions.

This is a possibly temporary solution to the background realization of delayed
resources. Each background-resource-map uses the same global (currently unbounded)
thread pool, but aims for utilizing only two threads at a time to realize resources
in order of priority as determined by an arbitrary selector function passed in.

Higher level api functions for working with databases

Namespace responsible for the creation, interpretation, and packing of entity ids.

Central namespace for specifying clojure print behaviors on the
top-level java Eva interfaces.

Aggregates usable in the :find specification of queries.

Contains helpers for reading data from a conformed pull spec.

Mostly involves normalizing pattern-data-literal from the grammar
into a form that's a bit more amenable for processing.

Tracing utilities to add toggleable tracing to the query engine.

Enable via setting the config option :eva.query.trace-logging or
the environment variable EVA_QUERY_TRACE_LOGGING to true.

Convenience namespace to refer to protocol methods and certain internal btree methods
all in one place. See eva.v2.datastructures.bbtree.api for implementation details and docs.

The function of this namespace is to collect the public-facing 'permanent' methods of the
btree code. As new versions are written, the constructors here should be updated to point
to the latest constructor code.

The fressian tags common to all versions -- mostly Clojure Core stuff.

A map-like structure with the following quirks:
- each key is associated with a vector of all values inserted at that key.
- `count' returns the sum of lengths of all vector values.
- it works as a priority-map, sorting each key by the length of its associated vector.
- Corollary: `first' returns the entry with the longest value vector.

Generic get/put-node methods wrapped over the value store protocol.
Non-version-specific. Pointers and Nodes in any version of the btree should
implement the NodeStorageInfo protocol and storage should just work.

Implementation of an append-only immutable vector in secondary storage.
This implementation should behave correctly and safely under concurrent
attempts to read and write. Writing to the end of the vector and reading from
any position in the vector should be O(1). This data structure is intended to
support the immutable write-ahead transaction log backing an Eva database.

Provides consolidated write & read handlers for use in various circumstances
depending on the content being handled.

Minimal Reimplementation of node.alpha using the jms.beta
code to make it JMS 1.1 compatible.

This messaging implementation was forked from
the local messaging node to provide a less
restricted more-nondeterministic broker.

Local connection for an EVA Database. Supports in-memory, h2 and sqlite.

Core logic for the transaction pipeline, provides the entry point for transaction
processing via the 'transact' function

Transaction pipeline related errors and error codes.

Protocols used in transaction pipeline.

Contains the logic for three major chunks of work in the transaction pipeline:
1. Resolve the unique-attribute-merging problem that arises from unique identity semantics.
2. Resolve temporary ids into permanent ids.
3. Eliminate redundant Adds or Retracts in tx-data.

Provides the logic for recursively flattening map entities in a transaction.

Defines concrete types for the fundamental Add and Retract transaction operations.

Defines a concrete type for Map Entity operations handled in the transaction pipeline.

Defines a concrete type for transaction functions handled in the transaction pipeline.

Provides the validation logic for a finalized batch of tx-data.