Tom
Tom
It's also the case for HTTP API, as there is no session being kept. If you `LET $name = "tobie"` in one request and then, `CREATE person SET name =...
For now can be worked around by defining default value on container field: ```sql DEFINE TABLE metrics SCHEMALESS; DEFINE FIELD custom ON metrics TYPE object VALUE {}; DEFINE FIELD custom.sales_difference...
Does this also add support for weeks in `timestamp_ceil` & `timestamp_floor` [date/time functions](https://questdb.io/docs/reference/function/date-time)?
Good luck on the hackathon then! 🙌
There was an issue already tracking this, here: https://github.com/surrealdb/surrealdb/issues/39
4️⃣ There is 4th scenario as well `CREATE ... CONTENT`: ```sql CREATE metrics CONTENT ( LET $sales = (SELECT quantity FROM sales); RETURN { sales: $sales } ) ``` ```json...
Oh, yeah, it's the semicolon after `CREATE whatever` that caused the Parse Error.
Anyhow, the API lacks consistency: ```sql DEFINE EVENT js_when_srql_then ON sometable WHEN function () { return this.event == "CREATE" } THEN (CREATE some_event_result); DEFINE EVENT js_when_srql_then ON sometable WHEN function...
From those options, my vote goes to keeping the semantics of SRQL with `$` prefix and direct variable, aka: ```js fn () { return $event == "CREATE" } ``` Because...
Ah, yes and no. There are a bunch of caveats with valid/invalid dates/times, and writing regex for that is complicated. Just expressing number range for 0-23 is messed up. As...