Hey Guys,
Just to expand on this a bit. When the Node.js SDK cannot identify the
data type of an object through our meta-data, it will fall back to decoding
as a raw buffer rather than fail entirely. You may want to try
{format:'json'} to force the value to be decoded as JSON regardless of the
meta-data. Additionally, if you upgrade to the latest 2.0 clients, the
meta-data used across all the clients is now in sync and this will happen
automatically.
Cheers, Brett
On Thursday, October 16, 2014 7:51:16 PM UTC-3, Nick Wood wrote:
>
> Server version is 2.5.1
>
> I've been storing documents using the .NET client, and when trying to
> retrieve them using the latest node.js 2.0.0 client, I'm getting a
> SlowBuffer object returned instead of a javascript object. For example:
>
> { cas: { '0': 792662784, '1': 1609732641 },
> value: <SlowBuffer 7b 22 63 6f 6e ...>
>
> I believe it's similar to this very old 1.x issue -
> http://www.couchbase.com/issues/browse/JSCBC-49
> <http://www.google.com/url?q=http%3A%2F%2Fwww.couchbase.com%2Fissues%2Fbrowse%2FJSCBC-49&sa=D&sntz=1&usg=AFQjCNGRNbs_eHW4RRoheNUay0Pe0_ueBg>
>
> I've tried setting { format: 'raw' } and { format: 'auto' } in my node
> client and I see no difference.
>
> Is there another format that would make this work?
>
> Is there a recommended approach to getting this to work with different
> clients? Reading and re-storing all documents to a new server using the
> .NET client would be an option if there's a flag that I can set to make it
> more compatible with other clients.
>
> Nick
>
--
You received this message because you are subscribed to the Google Groups
"Couchbase" 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.
