Expand description
IndraDB - a graph datastore.
IndraDB is broken up into a library and an application. This is the
library, which you would use if you want to create new datastore
implementations, or plug into the low-level details of IndraDB. For most
use cases, you can use the application, which exposes an API and scripting
layer.
Modules
Utility functions.
Structs
An edge.
Represents a uniquely identifiable key to an edge.
Represents an edge property.
Gets property values associated with edges.
The Error type.
An in-memory-only datastore.
A transaction for manipulating in-memory-only datastores.
Gets the edges associated with vertices.
Gets the vertices associated with edges.
Gets a range of vertices.
Gets a specific set of edges.
Gets a specific set of vertices.
An edge or vertex type.
The Error type.
A vertex.
Represents a vertex property.
Gets property values associated with vertices.
Enums
Specifies what kind of items should be piped from one type of query to
another.
A query for edges.
The kind of an error.
The kind of an error.
A query for vertices.
Traits
Specifies a datastore implementation.
Extension trait that specifies methods exposed by all edge queries.
Additional methods for
Result, for easy interaction with this crate.Specifies a transaction implementation, which are returned by datastores.
All datastore manipulations are done through transactions. Despite the
name, different datastore implementations carry different guarantees.
Depending on the implementation, it may not be possible to rollback the
changes on error. See the documentation of individual implementations for
details. Transactions are automatically committed on drop. Transactions
should be designed to not fail on commit; i.e. errors should occur when a
method is actually called instead.
Additional methods for
Result, for easy interaction with this crate.Extension trait that specifies methods exposed by all vertex queries.
Type Definitions
Convenient wrapper around
std::Result.Convenient wrapper around
std::Result.