Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Redash transform integer wrong, like, select 331451557290541101
See original GitHub issueExecute 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
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Error while writing query of existing query - Redash Discourse
Hey, I am writing this query using existing query. select query_1018.user, CAST(Date_1 as DATETIME), Date_2 , (Date_2 - Date_1) from ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
Noting here that the above example workaround with
char(1000)casting has another issue https://github.com/getredash/redash/issues/5504 when it goes through Redash’s query results.Casting to varchar works well also in that scenario. I.e.
select 10231293870128957129845712908471290341234123412::varchar