|
Previous
·
Next
|
Graham
|
Date: 3/27/2008 3:27 pm · Subject: JSON 2.x to_json vs encode_json · Rating: -1
We've been using to_json everywhere to do JSON encoding, but in any place where you may be storing UTF-8 data, you should use encode_json and decode_json instead. This was a problem for the poll, and is likely an issue elsewhere as well.
|
| Back to Top |
Rate [ | ]
|
| |
colink
|
Date: 3/27/2008 4:02 pm · Subject: Re: JSON 2.x to_json vs encode_json · Rating: 0
is it as simple as s/(from|to)(?=_json)/$1 eq 'from' ? 'decode' : 'encode'/esg;
|
| Back to Top |
Rate [ | ]
|
| |
Graham
|
Date: 3/27/2008 5:26 pm · Subject: Re: JSON 2.x to_json vs encode_json · Rating: 8
Should be pretty much that simple. I can't think of anywhere offhand where we would not want to use UTF8. On Mar 27, 2008, at 4:02 PM, <ckuskie@sterlink.net> <ckuskie@sterlink.net> wrote:
colink wrote:
is it as simple as s/(from|to)(?=_json)/$1 eq 'from' ? 'decode' : 'encode'/esg;
http://www.plainblack.com/webgui/dev/discuss/json-2_x-to_json-vs-encode_json/1
--
Plain Black, makers of WebGUI http://plainblack.com
|
| Back to Top |
Rate [ | ]
|
| |
|
|
Re: Goals by JT - Fri @ 12:31pm Re: Images in RSS-Syndicated asset by elnino - Fri @ 12:25pm Re: Images in RSS-Syndicated asset by ehab - Fri @ 11:52am Re: Images in RSS-Syndicated asset by elnino - Fri @ 11:47am
|