Keep in mind that since a CAS is a 64 bit integer you would need to pass
it around as a string. The 64 bit width is not merely theoretical but
rather quite common. This is the primary reason why the API maintains
this as an opaque object.
That being said, it should be simple to modify the bits here to also
accept properly formatted strings (but _not_ numbers) for CAS values.
https://github.com/couchbase/couchnode/blob/master/src/cas.cc#L66
On 04/30/2014 07:24 AM, Steven Barlow wrote:
So it's good to know that I'm not alone, but worrying to hear that this has
been an issue for so long. As far as I'm concerned it's a fairly major show
stopper bug in what I assumed would be a pretty heavily consumed and field
tested component.
Any further light you can shed will be appreciated Mark, and hopefully the
Couchbase guys can turn around a fix rapidly, as this issue is basically a
blocker for me adopting Couchbase.
Cheers,
Steven
--
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.
