Expand description
The backend. This contains the “low level” storage and query code, which is implemented as a json-like kv document database. This has no rules about content of the server, which are all enforced at higher levels. The role of the backend is to persist content safely to disk, load that content, and execute queries utilising indexes in the most effective way possible.
Structs§
- Backend
- Backend
Config - Backend
Read Transaction - Backend
Write Transaction - IdRaw
Entry - IdxMeta
- Limits
- Limits on the resources a single event can consume. These are defined per-event as they are derived from the userAuthToken based on that individual session
Enums§
- IdList
- The result of a key value request containing the list of entry IDs that match the filter/query condition.