Error parsing stringified JSON string

Question

Let's say I have an object:

person={'name':'john "Garfield"'};

And I convert it to a string:

JSON.stringify(person);
// RESULT: {"name":"john \"Garfield\""}

And then I store that string on MySQL or anything else and later I get that string on node.js (using interactive console):

string = '{"name":"john \"Garfield\""}';
// RESULT: {"name":"john "Garfield""}

Then I parse the object:

JSON.parse(string);
RESULT: SyntaxError: Unexpected token G

How can I parse stored json stringified string? I have them on MySQL and they loose their scaping slashes when requested by the MySQL library.

Niet the Dark Absol · Accepted Answer · 2012-10-13 15:19:15Z

3

You (should) notice that the backslashes have "gone missing" when you have the string. If it's stored in the database and retrieved from the database then the code should be working just fine. However, if you manually input that string to parse it out, then you need to escape the backslashes.

string = '{"name":"John \\"Garfield\\""}';

If the backslashes are getting lost during the MySQL insert, then try escaping them before inserting them.

answered Oct 13, 2012 at 15:19

Niet the Dark Absol

326k86 gold badges480 silver badges604 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Rodrigo Polo Over a year ago

The backslashes are getting lost during the retrieval, I have solved the issue with a REPLACE on the SELECT on MySQL but this kind of code looks dumb: REPLACE(field, "\\\\", "\\\\\\\\")

Niet the Dark Absol Over a year ago

They shouldn't be getting lost there... I'm not entirely sure what to suggest without seeing the full query code.

Rodrigo Polo Over a year ago

Damn... the issue was with this function: stackoverflow.com/questions/7744912/… - I was doing a full "back to basics" test when I found that some "%" get escaped when it doesn't need to be scaped ¬¬ the query works great without the replace using this lib: github.com/felixge/node-mysql

ebohlman Over a year ago

stackoverflow etiquette requires that you accept this answer, since it led to you solving your problem.

Rodrigo Polo · Accepted Answer · 2012-10-13 21:15:25Z

1

I have solved this issue with a REPLACE on MySQL, I don't understand why this have to be done this way, well, I understand but I don't like this solution, using node.js, and a MySQL library and calling MySQL from node here is the statement I did:

REPLACE(`field`, "\\\\", "\\\\\\\\") as field2

This looks dumb, but when you declare a string on node it is automatically unescaped, then this:

string = 'REPLACE(`field`, "\\\\", "\\\\\\\\") as field2';

becomes this:

REPLACE(`field`, "\\", "\\\\") as field2

And when is received by MySQL it becomes:

REPLACE(`field`, "\", "\\") as field2

I feel that it has to be another way!

answered Oct 13, 2012 at 21:15

Rodrigo Polo

4,9392 gold badges30 silver badges33 bronze badges

Comments

Tyler2P · Accepted Answer · 2023-02-08 19:43:38Z

0

Use encodeURI() and decodeURI() to save nested JSON in SQL database. This will escape everything for you.

edited Feb 8, 2023 at 19:43

Tyler2P

2,37030 gold badges26 silver badges34 bronze badges

answered Feb 6, 2023 at 17:27

Aaron Smith

11

Collectives™ on Stack Overflow

Error parsing stringified JSON string

3 Answers 3

4 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

4 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related