You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that when parsing BigInt values from MSSQL, Tedious converts them to strings even though the underlying readBigInt64LE returns a native JavaScript BigInt:
functionreadBigInt(buf: Buffer,offset: number): Result<string>{letvalue;({ offset, value }=readBigInt64LE(buf,offset));returnnewResult(value.toString(),offset);}
I'm curious about the reasoning behind this design decision. Is this related to:
JSON serialization compatibility?
Cross-environment support considerations?
Precision guarantees?
Framework compatibility?
Thanks for maintaining this library!
The text was updated successfully, but these errors were encountered:
I noticed that when parsing BigInt values from MSSQL, Tedious converts them to strings even though the underlying readBigInt64LE returns a native JavaScript BigInt:
I'm curious about the reasoning behind this design decision. Is this related to:
Thanks for maintaining this library!
The text was updated successfully, but these errors were encountered: