fdb-record-layer-core 4.1.9.0 API
This layer is designed to extend the FoundationDB key-value store by adding a record-oriented data model. Though this layer does not attempt to implement SQL, it does provide relational semantics (broadly defined). In particular, it attempts to provide solutions to:
- Schema management
- Index maintenance
- Query planning and optimization
The basic unit of data is the "record". This corresponds to a "row" in a traditional relational system or to a "document" in a document database. Records are grouped together into "record stores", which are somewhat analogous to a "database" in a traditional relational database, and each record also has a "type" which is somewhat (but not quite) analogous to a "table". (See, however, "Are record types tables?" in the FAQ for an explanation of the differences between the two concepts.)
For a more complete overview of the features and goals of the Record Layer, consult the Record Layer overview.
RecordCursor
s and
various IndexMaintainer
s for controlling concurrency in
read/write data paths.RecordStoreState
information.com.apple.foundationdb.synchronizedsession
package to support running operations in
synchronized sessions with FDBDatabaseRunner
s
and FDBRecordContext
s.BITMAP_VALUE
index entries.RelationalExpression
as a graph for both internal debugging purposes and for consumption by end-users.RelationalExpression
implementations
which will never be used outside of the planner.QueryPredicate
.QueryPredicate
s.Type
s using protobuf.Value
.Value
s.Value
translation algorithms.RecordQueryPlan
s.RecordCursor
for use in queries without a sorting index.