View Source API Reference Ecto.Adapters.FoundationDB v0.5.0

Modules

This module provides functions that are to be run by an operator, and not part of application code.

This exception is raised when there is a conflict in the tenant used.

This exception is raised when the application uses an Ecto feature that is not supported by the FoundationDB Adapter.

Opaque struct that represents an unresolved result set from some FoundationDB query operation.

Implement this behaviour to create a custom index.

This is Indexer keeps track of various actions for a Schema

The Ecto FoundationDB Adapter implements a Layer on the underlying key-value store provided by FoundationDB. Via this layer, some common data access patterns are achieved. For those familiar with relational databases such as Postgres, these patterns will be familiar. However, there are many differences (for example SQL is not supported), so this document seeks to describe the capabilities of the Ecto FoundationDB Layer in detail.

Implement this behaviour to define migrations for Ecto.Adapters.FoundationDB

A module for managing a sandbox FoundationDB cluster. This allows a developer to create a space under which it should be safe to write tests.

This module allows the application to create, open, and delete tenants within the FoundationDB database. All transactions require a tenant, so any application that uses the Ecto FoundationDB Adapter must use this module.

The default backend for EctoFDB multitenancy.

An experimental backend for EctoFDB multitenancy. It uses FDB's Tenants to guarantee that a given transaction cannot access keys from another tenant.

Versionstamping is a feature that allows you to create a unique identifier for a record that is guaranteed to be unique across all records in the database.