pankaj-ag
Hello
Let me define the problem first.
I have a jsonb database column called results in my Postgres DB. When I save a value (i.e 12\25) it saves like that in the DB.
{"attri": {"input": "12\\25"}}
Now I have a JSON string
"{ "custom_key": "@attri.input"}"
When I replace the above map values in this string I got the following results.
"{\"custom_key\": \"12\\25\"}"
All this is good and working as expected but when I try to decode this string into JSON
Like this Jason.decode("{\"custom_key\": \"12\\25\"}") it gives me an error.
I also try to escape the value before replacing it in string and in that case, it gives me the following results.
"{ \"custom_key\": \"\"12\\\\25\"\"}"
And I am not able to parse this string into JSON as well.
Please let me know in case I am missing something here or you need any other clarification on the problem.
Trending in Questions
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
al2o3cr
Forum tip: telling the reader “it gives me an error” is vastly less helpful than showing the reader the output of trying that:
Printing the string involved makes it clearer what’s going on:
So the JSON parser complains about the lone
\in the input.In your second example, this happens:
Now the extra
"s around12\\25throw the whole thing off.My advice: don’t try to replace values in JSON by string-replacing the whole thing - parse the JSON, do the replacements there, then re-encode.