Stop interpolating SurrealQL: use prepared statements for safe, cached queries
SurrealDB prepared statements bind parameters with $variable syntax, preventing injection and enabling server-side query plan caching.
Loading…
ReadMeFeed / Community knowledge
#surrealql
Real questions. Useful conversations. Find the people who know your stack.
surrealdbSurrealDB Upserts and Schema Type Validation: Why Your Update Created a Duplicate
SurrealDB upserts match only on the record ID, and type checks only exist once you define fields. Here's how UPSERT, DEFINE FIELD, and SCHEMAFULL interact — and how to verify the behavior on your own deployment.
Stop Using Join Tables: Managing Relationships with SurrealDB Record Links
Stop managing cumbersome join tables. Learn how to use SurrealDB Record Links and Graph Edges to simplify your schema and perform high-performance data traversals.
Ditch the Join Table: Modeling Relationships with SurrealDB Record Links and RELATE Edges
SurrealDB's record links and RELATE edges replace join tables with native graph relationships — here's a worked example, plus the referential integrity trade-off you need to plan for.
Record Links or RELATE Edges? Modeling Relationships in SurrealDB
SurrealDB offers record links and RELATE graph edges for modeling relationships. Here's a worked follow-graph example and a practical rule for choosing between them.
SurrealDB FETCH Clause: One-Hop Graph Traversals in SurrealQL
SurrealDB's FETCH clause resolves one-hop record links in a single SELECT, embedding related records directly. This guide shows the schema setup, a worked example, performance limits, and the most common mistakes that cause silent failures.
Diagnosing and Resolving Memory Exhaustion in SurrealDB
A diagnostic guide for resolving Out of Memory (OOM) errors in SurrealDB, covering unbounded result sets, graph traversal explosions, and MVCC overhead.
SurrealDB Record ID constraints in schema-full mode
SurrealDB utilizes a unique record ID system that allows direct access to documents by combining table names and identifiers. In a schema-full environment, DEFINE TABLE is used to enforce strict type constraints on fields to ensure data consistency. While field-level types are strictly enforced, there is uncertainty regarding the ability to constrain the for
SurrealQL FETCH clause depth and performance limits
SurrealDB uses the FETCH clause to resolve record IDs into full objects, effectively flattening graph relationships into a single query response to minimize network round-trips. When dealing with deeply nested record links, there is a potential for performance degradation as the traversal complexity increases. It is unclear how the database manages memory an