Hi all,
I'm having some serious trouble with backslash characters within a json
representation string in SQL queries.
It seems the parser is doubling backslashes in strings and it causes an
exponential growth of them, at each update.
A simple example:
*update person set test = {'@type':'d','a':'some \\ text'} where name =
"john"*
*select test from person where name = "john"*
and I get: *{"@type":"document","@version":0,"a":"some \\\\ text"}*
that it's wrong because the first backslash of the original json string is
meant to escape the second single backslash.
see [2.5. Strings] of https://tools.ietf.org/html/rfc4627
Now, if I get the output string from a select, I do my stuff, and then I
recode it in a json representation string to get a record updated, the
encoder will write an escaped version of the backslashes sequence (so they
will become 4) and the SQL parser will double them again.
Have anyone an idea how to prevent the parser to act in a such behaviour?
Thanks
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
