Replies: 4 comments 1 reply
-
There is no way to avoid when using the bash shell. The rqlite shell is doing the escaping for you: https://github.com/rqlite/rqlite/blob/master/cmd/rqlite/execute.go#L38 Does that answer your question? It's a limitation of bash, not something specific to rqlite. |
Beta Was this translation helpful? Give feedback.
-
You could also make it easier for yourself, perhaps, by writing a small tool that you can call directly from bash -- something built using the Python or Go client libraries. |
Beta Was this translation helpful? Give feedback.
-
So an interesting thing is I tried this using Postman:
And I get the same: |
Beta Was this translation helpful? Give feedback.
-
Without knowing what Postman is doing under the covers, it's hard to offer to an opinion. |
Beta Was this translation helpful? Give feedback.
-
Sorry for the question. I'm a little confused and this maybe stupid.
If I start the Rqlite shell and do this:
All seem to work fine.
If I try to do this via cURL:
It doesn't work. However, if I do this:
It works.
Is there a way to avoid having to escape everything and send plain JSON structures via the HTTP API like I do using the rqlite shell ?
Based on my schema the "interests" column has a type of JSON, so should this not work ?
Beta Was this translation helpful? Give feedback.
All reactions