Closed AkshayBhimani closed 1 year ago
Hi, thank you for your bug report! :) This is related to an existing issue: https://github.com/libsql/libsql-client-ts/issues/32
Basically, this is expected default behavior: we chose to convert SQLite integers to JavaScript number
s by default, but we don't yet provide a way to opt into using bigint
s instead.
What would be your preferred solution? Would you prefer if we returned integers as bigints by default?
Fixed in version 0.4.2, you can use Client.intMode
or Stream.intMode
to choose the JavaScript representation of SQLite integers: either number
, bigint
or string
.
When trying to fetch data from Turso DB where one table column has long integer (for me integer with 19 digit ). It is giving error cannot be safely represented as a JavaScript number
Full trace :