ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #surrealdb
Goal: Configure the SurrealDB JavaScript client to trust a custom certificate authority while still enforcing hostname verification during TLS handshake. Constraints: The client’s `tls` option accepts a `ca` array for custom CAs and a `rejectUnauthorized` flag that mirrors Node.js TLS settings. Setting `rejectUnauthorized: false` disables all validation, but
Record-Level Permission Filtering SurrealDB utilizes DEFINE TABLE and DEFINE FIELD statements to implement fine-grained access control. These permissions are evaluated during the query execution phase, effectively acting as a filter on the records returned to the user based on the authenticated session's properties. Consistency in Aggregations When executing
SurrealDB utilizes PERMISSIONS clauses on tables and records to enforce fine-grained access control. These expressions typically evaluate the current session's user attributes against record data to determine if a SELECT , CREATE , UPDATE , or DELETE action is permitted. When implementing DEFINE ROLE for scalable management, there is a need to handle overlap
Integration boundary I am wiring the official SurrealDB Rust driver ( surrealdb crate) against a local SurrealDB server started in memory-only mode ( mem:// ) for an integration-test suite. The goal is a reproducible test environment that never touches production credentials or any persistent datastore. Constraints and uncertainty The server is launched with