I did the same thing :) I inserted lots of bigDecimal in Cqlsh and read it from my C# client. Then I did the opposite, inserts BigDecimal from C# and query it from cqlsh. Once both directions worked, I had unit tests to make sure data is cross platform compatible.
I know older versions of FluentCassandra handled BigDecimal incorrectly, so any BigDecimal inserted from C# caused a stack overflow in cqlsh. On Mon, Feb 24, 2014 at 1:49 PM, Ben Hood <0x6e6...@gmail.com> wrote: > Hey Paul, > > On Mon, Feb 24, 2014 at 6:40 PM, Paul "LeoNerd" Evans > <leon...@leonerd.org.uk> wrote: > > And the unit tests live here: > > > > > https://metacpan.org/source/PEVANS/Protocol-CassandraCQL-0.11/t/02types.t#L111 > > Very cool - I'll port these examples to the gocql marshaling test > suite - kudos to you for reverse engineering the encoding :-) >
