But then if the JSON is sent as a string property of a bigger object, it'll 
have to be parsed by JavaScript on the browser side. That is undesirable.

On Thursday, August 10, 2017 at 1:21:54 PM UTC-7, Shawn Milochik wrote:
> On Thu, Aug 10, 2017 at 4:20 PM, Dmitriy Cherchenko <dcher...@gmail.com 
> <javascript:>> wrote:
>> Hi Shawn,
>> Thank you for your quick reply!
>> I’m not having any issues retrieving data from the database. I’m only 
>> concerned that the unmarshalling and marshalling processes seem needless 
>> and a little risky especially on big JSON objects.
> Sure. If you just want to pull it out of the DB and return it as a string, 
> there's no reason to use the encoding/json package.

You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to