If anyone else runs into this... The 2.x .NET client seems to store the
documents in a more compatible way. After upgrading, I read and stored the
same document to the same server, at which point the nodejs client was able
to read it just fine.
If there's a quick trick to get this working with the .NET 1.3.x client,
I'd love to hear it as I'm not in a position to begin using the .NET 2.x
client in production.
Nick
On Thursday, October 16, 2014 4:51:16 PM UTC-6, 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
>
> 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.
