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

About MySQL non-UTF8 Encoding support like latin1 or GBK #4747

Closed
myonlylonely opened this issue Mar 20, 2020 · 1 comment
Closed

About MySQL non-UTF8 Encoding support like latin1 or GBK #4747

myonlylonely opened this issue Mar 20, 2020 · 1 comment

Comments

@myonlylonely
Copy link
Contributor

Does redash support non-UTF8 encoding in MYSQL?
I have a MySQL database in latin1, I have to use CONVERT(CAST(character_name AS BINARY) USING gbk) to convert every string field to display string correctly. There are too many string fields, so it is a little bit of annoyed.
Would Redash consider supporting a config or settings in data source page to let user choose which encoding should Redash use? Or is there any more appropriate workaround or solution?

@support
Copy link

support bot commented Mar 20, 2020

👋 @myonlylonely, we use the issue tracker exclusively for bug reports and planned work. However, this issue appears to be a support request. Please use our forum to get help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant