Skip to content
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

Closed
2 tasks done
Calemy opened this issue Sep 24, 2022 · 5 comments
Closed
2 tasks done

Bug: Escaped characters not working on create content #1212

Calemy opened this issue Sep 24, 2022 · 5 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Calemy
Copy link

Calemy commented Sep 24, 2022

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?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Calemy Calemy added bug Something isn't working triage This issue is new labels Sep 24, 2022
@ItsValerius
Copy link

I think this is the same issue as #90, which is supposed to be fixed in the upcoming release.

@tobiemh tobiemh removed the triage This issue is new label Sep 24, 2022
@tobiemh tobiemh added this to the v1.0.0-beta.8 milestone Sep 24, 2022
@tobiemh
Copy link
Member

tobiemh commented Sep 24, 2022

Hi @Calemy yes that's right. This is the same issue as #90, #137, #245, and #1202!

@Calemy
Copy link
Author

Calemy commented Sep 24, 2022

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! :)

@tobiemh
Copy link
Member

tobiemh commented Sep 24, 2022

@Calemy yes we expect that issue to be resolved with 1.0.0-beta.8 too!

@Calemy
Copy link
Author

Calemy commented Sep 24, 2022

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!

@Calemy Calemy closed this as completed Sep 24, 2022
@tobiemh tobiemh self-assigned this Sep 24, 2022
tobiemh added a commit that referenced this issue Sep 26, 2022
tobiemh added a commit that referenced this issue Sep 26, 2022
Closes #90
Closes #137
Closes #245
Closes #1202
Closes #1212
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants