-
Notifications
You must be signed in to change notification settings - Fork 93
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
Int64 columns are loaded as binary columns in PowerBI #445
Comments
I also tried columns of other data types, including Int32, UInt32, UInt64. |
Hi @traceon , could you please give some hints on how to debug/fix this issue? Thank you! |
The problem seems to come from the fact that At least in my testing, when I remove this type name overlap—either by completely removing unsigned types or by assigning unique names to each type—the problems seem to go away, and all columns appear as whole numbers in Power BI. Using unique names for each type is indeed the correct approach. In fact, the ODBC documentation requires that the type names returned by However, this change might break some backward compatibility, so further investigation is needed. Additionally, the |
@nudles, am I correct in understanding that you can change the type of the |
ClickHouse version: 24.7.1.2092
ODBC version: 1.2.1.20220905
PowerBI version: 2024 July
Table DDL
After creating the table, I tried to load it from PowerBI via ODBC driver. However, only the 'name' column is visible.

The LocationID column is missing.
In the transform view, it shows that the 'location' column's type is binary. I changed it to number manually.

Then I can see the location column
The question is how can we change ODBC driver to fix the data type mapping?
Thank you!
The text was updated successfully, but these errors were encountered: