Bug: LET statement variables do not stay across queries in the CLI REPL

[peteole]

Describe the bug

The value of let statements is instantly lost once they have been executed. Running

-- Define the parameter
LET $name = "tobie";

And then

-- Use the parameter
CREATE person SET name = $name;

results in the name field not being set:

> LET $name = "tobie";
[{"time":"17.363µs","status":"OK","result":null}]
> CREATE person:3 SET name = $name;
[{"time":"116.22µs","status":"OK","result":[{"id":"person:3"}]}]

However interestingly copying both statements together into the repl works as expected.

Steps to reproduce

Run

> LET $name = "tobie";
[{"time":"17.363µs","status":"OK","result":null}]
> CREATE person:3 SET name = $name;
[{"time":"116.22µs","status":"OK","result":[{"id":"person:3"}]}]

Expected behaviour

The value is stored in the variable.

SurrealDB version

surreal 1.0.0-beta.6 for linux on x86_64

Contact Details

peteole2707@gmail.com

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[tobiemh]

Hi @peteole thank you for this issue!

Currently the REPL opens a new connection to the database for each submitted query, and therefore all context between queries is reset.

We'll be changing this really soon so that it connects over the WebSocket connection instead, meaning that all context is kept between submitted queries.

That should then fix this issue.

[tobiemh]

This is also related to #35

[tomsseisums]

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 = $name; in another request, it will have the same problem.

Any comments on that @tobiemh, as if that's supposed to be supported in future or?

[rushmorem]

Hi @tobiemh. Kindly assign this to me.