Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UInt64 is not recognized to Tableau #365

Closed
dima-altinity opened this issue Jul 16, 2021 · 3 comments · Fixed by #356
Closed

UInt64 is not recognized to Tableau #365

dima-altinity opened this issue Jul 16, 2021 · 3 comments · Fixed by #356
Assignees

Comments

@dima-altinity
Copy link

Tableau generates error if you try to use open table with UInt64 type.

Error is: An error occurred while loading the data.
Cannot interpret '18150585289071012696' as signed 64-bit integer: stoll argument out of range

Steps to reproduce:
Connect to ClickHouse Playground database from Tableau and try to open "hits_100m_obfuscated" table.

@traceon traceon mentioned this issue Jul 21, 2021
@nvm1
Copy link

nvm1 commented Jul 22, 2021

@dima-altinity , I guess the problem is that Tableau does not support unsigned integers :( We encountered this problem as well and the only possible solution here is to cast to string columns which values might exceed int64 values.

https://help.tableau.com/current/api/hyper_api/en-us/reference/sql/datatype-numeric.html

@nvm1
Copy link

nvm1 commented Jul 22, 2021

@dima-altinity , I guess the problem is that Tableau does not support unsigned integers :( We encountered this problem as well and the only possible solution here is to cast to string columns which values might exceed int64 values.

https://help.tableau.com/current/api/hyper_api/en-us/reference/sql/datatype-numeric.html

Well, noticed that it's linked to #356 and I see that you will interpret those large values as string. That would be great. Thank you!

@traceon
Copy link
Collaborator

traceon commented Jul 22, 2021

Yes, somehow Tableau was binding a signed 64-bit integer to columns that were reported as SQL_BIGINT with unsigned attribute of the column set to true. So the only workaround here, is just to report those columns as strings to Tableau.

@traceon traceon added bug and removed bug labels Jul 25, 2021
@traceon traceon self-assigned this Jul 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants