Redash transform integer wrong, like, select 331451557290541101

[guzhenping]

Execute sql ：

select 331451557290541101 

the result: 331,451,557,290,541,120.00, they are not equal.

Redash can not support the type of bigint. l think it's a bug.

Technical details:

• Redash Version: 4.0.1
• Browser/OS: chrome
• How did you install Redash: developer user-defined

[kyoshidajp]

Hi @guzhenping.

Probably, because the number exceeds the max number which will be able to treat as JSON.

For example select 9007199254740992 returns 9,007,199,254,740,992. But select 9007199254740993 returns 9,007,199,254,740,992.

To fix this, first, parses as a string when making the response and returns it in server-side. Second, parse as a string and display as an integer in client-side.

[rusq]

Hitting the same issue on version 7 (obviously because nothing has changed since this issue was discovered)

[liambinnsconroy]

Bump. Any update on this? Pretty annoying, our users are getting confused.

[susodapop]

I reproduced this on our preview instance.

[arikfr]

Looks like we can address this with https://www.npmjs.com/package/json-bigint. Just need to figure out if there are any performance implications.

[stefafafan]

I will link a workaround for this issue (casting to char) because there seemed to be no comments about it in this issue.

bro , yes working once i cast bigint to char in sql , like SELECT cast(uuid as char(408))
#5012 (comment)

example:

i wonder if there is anyway to fix this issue because casting to char everytime is a bit annoying. 😢 using json-bigint?

[RedBulli]

Noting here that the above example workaround with char(1000) casting has another issue #5504 when it goes through Redash's query results.

Casting to varchar works well also in that scenario. I.e.
select 10231293870128957129845712908471290341234123412::varchar