#community-help

Handling uint64 in Typesense

TLDR JinW inquired about handling uint64 in Typesense. Jason suggested using strings or reducing the granularity of values. Meanwhile, Harrison raised a point about database types.

17mo

Join the chat

Apr 14, 2022 (17 months ago)

Photo of md5-be53735a2b0297bb542711c1d2ecea45

JinW

12:12 AM

How do i handle uint64 beside using it as string?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

12:13 AM

Typesense does have an int64 data type. Unless you specifically meant unsigned int 64...

JinW

12:13 AM

Yes, unsigned uint64

Jason

12:14 AM

Strings would be the only way at the moment, for integers larger than (signed) int64

12:15

Jason

12:15 AM

Could you open a feature request on Github issues along with your use case for this?

12:16

Jason

12:16 AM

Or another work-around I can think of is reducing the granularity/precision of the values so they fit in int64

JinW

12:27 AM

Thanks, I was just making sure, We use uint64 for our primary id in our database and don't really have a use case for it.

Photo of md5-43a35158b04c9c49110114370dbeae06

Harrison

08:03 AM

interesting, what database? Normally they tend to be signed integer either explicitly or implicitly

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Discussion on Capacity to Represent BigInt

ilia inquired about adding unsigned int64 for BigInt representation. Kishore Nallan suggested no immediate plans, but highlighted a workaround and also warned about misusing float for large values.

1mo

Posting int64 values to API using JSON in Typesense

Patrick requested assistance in posting an int64 document to an API using JSON with Typesense due to JSON's large number limitations. Jason clarified the JSON library at Typesense does support int64.

1mo

Resolving Typesense Cloud and Firebase Timestamp Error

Eoin faced an issue with Firebase timestamp when setting up Typesense Cloud. Jason suggested converting timestamps to Unix and sync them as int64 fields in Typesense.

21mo

Typesense Non-String Field Query Workarounds

Carl seeks advice on querying non-string fields in Typesense. Kishore Nallan suggests using a string version, and Jason proposes the string* data type. Carl is considering these options.

20mo

Troubleshooting Typesense Document Import Error

Christopher had trouble importing 2.1M documents into Typesense due to memory errors. Jason clarified the system requirements, explaining the correlation between RAM and dataset size, and ways to tackle the issue. They both also discussed database-like query options.

8mo