Compare common GraphQL queries against similar SurrealQL SELECT patterns
SurrealDB’s GraphQL layer turns each table into list fields (for example person) and _get_<table> helpers for a single record by id. Under the hood these map to SurrealQL-style reads (typically SELECT). The SurrealQL here is a rough equivalent for the same or similar data shape.
Before trying the examples, enable GraphQL and define data in the current namespace and database (see GraphQL overview using DEFINE CONFIG GRAPHQL AUTO). The snippets below assume:
Namespace main, database main
Root authentication root / secret
A person table with name and age, and records person:simon and person:marcus as in GraphQL via HTTP
curl -X POST -u "root:secret" -H "Surreal-NS: main" -H "Surreal-DB: main" -H "Accept: application/json" \ -d '{ "query": "query { _get_person(id: \"simon\") { id name age } }" }' http://localhost:8000/graphql
Limit how many records are returned
GraphQL uses limit (and optional start for offset). SurrealQL uses LIMIT / START and ONLY to return a single record as opposed to an array containing a single record.
curl -X POST -u "root:secret" -H "Surreal-NS: main" -H "Surreal-DB: main" -H "Accept: application/json" \ -d '{ "query": "query { person(limit: 1) { name age } }" }' http://localhost:8000/graphql
Filter records
GraphQL accepts filter or where with the generated input type for the table (for example _filter_person). For a scalar field, use comparison keys such as eq, ne, gt, and lt where the schema allows them.