Open gramian opened 5 months ago
It should be BUCKET:myparam
since then the parameter is not identified as such.
Sorry, I didn't notice the parameter. Correct, you can't use parameters there.
Too bad. So, does this bug report become a feature request or is this too unlikely to be implemented and should hence be closed?
Hmm, so I tried using
wget -qO- http://localhost:2480/api/v1/query/test --post-data='{"language":"sql","params":{"myparam":"BUCKET:mybucket"},"command":"SELECT FROM :myparam"}' --user root --password arcadedb
which errors, but
wget -qO- http://localhost:2480/api/v1/query/test --post-data='{"language":"sql","params":{"myparam":"doc"},"command":"SELECT FROM :myparam"}' --user root --password arcadedb
works. So can you describe what the syntactic rule is, so I can add it to the docs?
If it works without the BUCKET:
prefix, then it should be easy to implement it. I'm ok with this as an enhancement.
ArcadeDB Version:
ArcadeDB Server v24.6.1-SNAPSHOT (build 6ff2d86d488fe6b3ca20f7a6554160d6017af118/1716919859476/main)
OS and JDK Version:
Running on Mac OS X 12.7.5 - OpenJDK 64-Bit Server VM 17.0.11 (Homebrew)
Using a parameter in POST request query where the parameter specifies a bucket name errors. This is maybe because the double colon, ie
BUCKET::param
cannot be parsed?Expected behavior
Succesful query in bucket
Actual behavior
Error on command execution
```Steps to reproduce