WebdaQL

Operators

= equal to
< less than
> greater than
<= less than or equal to
>= greater than or equal to
IN array
LIKE

AND:
OR:

Precedence
a AND b OR c is equivalent to (a AND b) OR c
a AND b OR c AND d is equivalent to (a AND b) OR (c AND d)

Order By

You can use ORDER BY to order the results, this is not a hard requirements to manage it on underlying Store.

Currently, MongoDB, Postgres, File and Memory have a full ORDER BY capabilities

DynamoDB have some hard limitation, only the sortKey can be ordered and every other ORDER BY clause will be ignored

FireBase have also limitations, only the defined index with their direction will be able to be used, every other ORDER BY clause will be ignored

Limit and Offset

To define the LIMIT just add LIMIT

Statements

WebdaQL also parses SELECT f1, f2 [WHERE ...], DELETE [WHERE ...] [LIMIT n] and UPDATE SET a = v [WHERE ...] [LIMIT n] (uppercase keywords only). The Query operations exposed to clients (REST, gRPC, MCP, GraphQL) take a filter only and refuse them with a 400. DELETE and UPDATE run through useRepository(Model).deleteMany() / updateMany(), which bypass events, hooks, validation and permissions. See Statements.

Aggregation

SELECT status, COUNT(*) AS n, SUM(points) AS total WHERE ... GROUP BY status ORDER BY total DESC LIMIT 10 parses into an aggregation, the string form of Model.aggregate(). The uppercase words COUNT, SUM, AVG, MIN, MAX, AS, DISTINCT and GROUP BY are now reserved (a breaking change for attributes with those uppercase names; lowercase names are unaffected). See Statements.