Why there is no SQL box yet
The requirement for this feature is strict: a restricted engine with no network or extensions, complete-result export, and no 64-bit integers or decimals coerced through floating point. Small in-browser SQL libraries commonly convert numbers to JavaScript floats, which would silently change values like 9007199254740993. A WebAssembly database engine meets more of the requirements but adds tens of megabytes and needs a separate review. Until one is qualified, the feature is marked UNSUPPORTED.
The workbench above runs the equivalent of SELECT region, COUNT(*), SUM(amount), AVG(amount) FROM sales WHERE status = ‘paid’ GROUP BY region ORDER BY SUM(amount) DESC, as three recipe steps. Each step shows its intermediate result, which a single SQL statement would not.
Translating common SQL
WHERE → Filter rows. SELECT columns → Select / reorder / drop. GROUP BY with aggregates → Group & aggregate. ORDER BY → Sort (stable). JOIN → Join file, with a cardinality preview. UNION ALL → Append file. DISTINCT → Deduplicate. LIMIT → Sample rows with “First rows”. Window functions and arbitrary expressions are not supported yet.
Questions
Will SQL be added?
It is planned as a restricted, local-only workspace once an engine passes the exactness and no-network requirements. No date is promised.
Can recipes do everything SQL can?
No. Recipes cover filtering, projection, grouping, joins, unions, distinct and ordering. Computed expressions, window functions and subqueries are not available.
Is the query-style recipe exact?
Yes. The sum and mean in this example use exact decimal arithmetic, and the recipe can be exported and replayed.