typesense

Any plans adding unsigned int64? Faced issue representing BigInt, and using string is suboptimal.

No plans at the moment, can you please create an issue on Github for us to track? We pick up tasks based on feedback from the community.

One really hacky way (as workaround) to represent uint64 is via two int64 fields. But you have to unpack and pack the variables on both read and write.

Thanks! I actually realised unsigned int64 doesn't cut for me. So f64 ( I think it's used in Typesense for `float` ) works fine for me, as I need to represent js BigInts.

float is 32 bits. If you try to store large values it will truncate.

Thanks, good to know. Luckily precision is not critical in my current use case.