Crate indradb [−] [src]
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
tests |
Unit tests for datastore implementations. |
util |
Utility functions. |
Macros
define_test |
Defines a unit test function. |
full_test_impl |
Use this macro to enable the entire standard test suite. |
Structs
Edge |
An edge. |
EdgeKey |
Represents a uniquely identifiable key to an edge. |
EdgeMetadata |
Represents edge metadata. |
Error |
The Error type. |
MemoryDatastore |
An in-memory-only datastore. |
MemoryTransaction |
A transaction for manipulating in-memory-only datastores. |
Type |
An edge or vertex type. |
ValidationError |
The Error type. |
Vertex |
A vertex. |
VertexMetadata |
Represents vertex metadata. |
Enums
EdgeDirection |
Specifies what kind of items should be piped from one type of query to another. |
EdgeQuery |
A query for edges. |
ErrorKind |
The kind of an error. |
ValidationErrorKind |
The kind of an error. |
VertexQuery |
A query for vertices. |
Traits
Datastore |
Specifies a datastore implementation. |
ResultExt |
Additional methods for |
Transaction |
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. |
ValidationResultExt |
Additional methods for |
Type Definitions
Result |
Convenient wrapper around |
ValidationResult |
Convenient wrapper around |