-
Notifications
You must be signed in to change notification settings - Fork 823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Escaped characters not working on create content #1212
Comments
I think this is the same issue as #90, which is supposed to be fixed in the upcoming release. |
I do apologize for the duplicate since i've not been able to find it under the keywords i used myself but i'm glad that it already is a known issue and hopefully is fixed soon. If i'm not mistaken the freezing in the nodejs library is already known as well? It makes my database's cpu usage skyrocket anytime something like that happens. Thank you regardless for your time! :) |
@Calemy yes we expect that issue to be resolved with 1.0.0-beta.8 too! |
awesome, i'm hyped and i wish you the best in the future. I'll try to contribute to the nodejs library since i plan to use this as my go-to database! |
Describe the bug
I'm trying to insert a documents that has escaped characters in it.
When trying to insert that document, it does not work.
It gives following error:
{
"code": 400,
"details": "Request problems detected",
"description": "There is a problem with your request. Refer to the documentation for further information.",
"information": "There was a problem with the database: Parse error on line 1 at character 20 when parsing 'CONTENT { name: "\tkotoko" }'"}
Steps to reproduce
start surrealdb
log into surrealdb-cli
create anything that has an escaped character in the content
example:
CREATE person:1 CONTENT { name: \tkotoko }
Expected behaviour
that it inserts the document with the escaped characters
SurrealDB version
surreal 1.0.0-beta.7 for windows on x86_64
Contact Details
nanoo@catboy.best
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: