mirror of
https://github.com/clockworklabs/SpacetimeDB.git
synced 2026-06-28 00:38:30 -04:00
cf73acff92
# Description of Changes Adds primary keys to procedural views in C++. This mirrors the work from #5111, #5246, and #5327 adding the feature and the docs changes. # API and ABI breaking changes None # Expected complexity level and risk 3 # Testing - [x] Equivalent tests as were added in #5111 and #5246 for rust, typescript, and C#
SpacetimeDB C++ Module Library Internal API
This directory contains the internal implementation of the SpacetimeDB C++ Module Library, matching the design of the C# bindings.
Overview
The Internal API provides:
- Module Definition Management: Automatic generation of module definitions using autogenerated types
- Type Registration: Type-safe registration system for tables and reducers
- FFI Wrappers: Safe wrappers around the SpacetimeDB ABI
- Table Operations: Type-safe CRUD operations on tables
- Reducer System: Framework for implementing reducers with proper serialization
Directory Structure
-
autogen/- Autogenerated types from Rust definitions (RawModuleDefV9, RawTableDefV9, etc.) -
Module.h/cpp- Main module management and registration -
FFI.h/cpp- Foreign Function Interface definitions
Key Components
1. Module Registration
The Module class is a singleton that manages:
- Table registration
- Reducer registration
- Type registration
- Module description generation
- Reducer invocation
2. Autogenerated Types
All module definition types are generated from the Rust codebase:
RawModuleDefV9- Main module definitionRawTableDefV9- Table definitionsRawReducerDefV9- Reducer definitionsTableAccess,TableType, etc. - Enums and supporting types
3. Table Implementation
Tables are implemented using the SPACETIMEDB_TABLE macro system:
- Define row types with field registration using
SPACETIMEDB_MODULE_STRUCT(modules) orSPACETIMEDB_STRUCT(clients) - Register tables with
SPACETIMEDB_TABLE(Type, "name", Access, ...constraints) - Use
ctx.db.table<T>("name")for table operations (insert, delete) - Tables are automatically registered during module initialization via
__preinit__functions
4. Reducer Implementation
Reducers are implemented using unified macro system:
SPACETIMEDB_REDUCER(name, ReducerContext ctx, ...params)- User-defined reducersSPACETIMEDB_INIT(name, ReducerContext ctx)- Module initializationSPACETIMEDB_CLIENT_CONNECTED(name, ReducerContext ctx)- Client connection handlerSPACETIMEDB_CLIENT_DISCONNECTED(name, ReducerContext ctx)- Client disconnection handler- The macros handle serialization, registration, and ABI integration automatically
Usage Example
// Define row type with field registration
struct Person {
uint32_t id;
std::string name;
uint8_t age;
};
SPACETIMEDB_MODULE_STRUCT(Person, id, name, age);
// Define table with constraints
SPACETIMEDB_TABLE(Person, "people", Public,
PrimaryKeyAutoInc(id),
Index(name)
);
// Define reducer with ReducerContext
SPACETIMEDB_REDUCER(add_person, ReducerContext ctx, std::string name, uint8_t age) {
// Access table and insert record
Person person{0, name, age}; // id will be auto-generated
ctx.db.table<Person>("people").insert(person);
LOG_INFO("Added person: " + name);
}
// Lifecycle reducers
SPACETIMEDB_INIT(init, ReducerContext ctx) {
LOG_INFO("Module initialized!");
return Ok();
}
SPACETIMEDB_CLIENT_CONNECTED(on_connect, ReducerContext ctx) {
LOG_INFO("Client connected!");
return Ok();
}
Migration from Old API
See MIGRATION_GUIDE.md for detailed steps on migrating from the manual module definition approach to this new Internal API.
Future Improvements
- Automatic BSATN serialization generation
- Macro-based table/reducer definitions
- Query builder API
- Index management