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
#query-parameters
Real questions. Useful conversations. Find the people who know your stack.
surrealdbFeathers service pagination without explicit `paginate.max` leaves `$limit` unbounded per adapter
Feathers services accept a paginate object with default and max properties, but the framework does not impose a built-in upper bound on the $limit query parameter when max is omitted. Pagination enforcement is delegated to the underlying database adapter, so the effective ceiling for an unbounded $limit can differ between Knex, Sequelize, Mongoose, and the m
feathersjsEnvoy RouteMatch query_parameters handling of duplicate query keys
Designing routing rules that depend on query parameters requires a clear definition of how Envoy interprets a request when the same query key appears multiple times. Envoy RouteMatch supports a query_parameters list with equality, prefix, suffix, regex, or presence matchers for a single key. The documented matcher types do not specify handling of duplicate k
Bounding Limit and Offset Query Parameters in Fastify Route Schemas
Goal: Validate limit and offset query parameters in Fastify route schemas so large dataset endpoints cannot return unbounded result sets. Fastify does not enforce a global maximum page size. Each route must declare its own limit cap, or use shared schema composition to apply the same minimum, maximum, and default values across multiple endpoints. Offset-base
fastify