Bigint columns are being returned as strings

When querying a bigint column the result is coming back as a string. Quick example:

CREATE TABLE test (
    col_bigint bigint,
    col_int int,
    col_smallint smallint,
    col_tinyint tinyint,
    col_float float,
    col_decimal decimal(9,4)
);

Running the query select * from test returns:

[ { col_bigint: '1',
col_int: 1,
col_smallint: 1,
col_tinyint: 1,
col_float: 1.11,
col_decimal: 1.11 } ]

This is against Azure SQL Database V12. Have not tested other versions of SQL Server.

[tracker1]

@jtmilne Because of the nature of JS numbers, you can’t really tell without extra computation of a bigint will fit in the safe integer space (52-bits) of a 64-bit floating point number… If you need something you can do calculations against you can use bignum or another npm module for dealing with the larger numbers… If you know you aren’t going to exceed 52-bits, you can coerce the value via parseInt(value,10) for those fields… don’t use bitwise coersions (~~value will give you a 32bit number)… prefer parseInt(x,10), or +value … Also, make sure to compare against Number.MAX_SAFE_INTEGER and MIN_SAFE_INTEGER before using said number as an integer… not to mention bounds checking any computed results.

[jtmilne]

Makes sense. In my case I am just reading a bigint from one table and using it as a parameter for other queries (insert, update, select) so I am not concerned of the integrity of the source number.

Thanks.