-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Clickhouse column name encoding problem #4677
Comments
I think that #4627 might fix this. What commit are you on? |
Im on 9.0.0-alpha |
Just to confirm, the version you had with the problem, already had |
Correct. I just appended the encoding to the "data" that was there already and tested it. |
Issue Summary
Alias column name contains non 'latin-1' characters return encoding error.
For example : select count(*) as 'כמות'…
Error message: 'latin-1' codec can't encode characters in position 285-288: Body ('כמות') is not valid Latin-1. Use body.encode('utf-8') if you want to send it encoded in UTF-8.
BTW, This works fine with other data source like mysql.
Steps to Reproduce
This is the first step
Create a query with ClickHouse as the data source
This is the second step, etc.
Add a column alias in utf8 chars like : select colum1 as 'ש'
Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
I expected to see the column alias like I do with mysql data source .
No problem with the 'utf-8' data, so probably column names should support 'utf-8' charset as well.
This used to work with the older version (v8)
Technical details:
9.0.0-alpha
Chrome
Docker Based Developer Installation
The text was updated successfully, but these errors were encountered: