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

encoding issues #6

Open
joaopaulofilho opened this issue Feb 8, 2017 · 1 comment
Open

encoding issues #6

joaopaulofilho opened this issue Feb 8, 2017 · 1 comment

Comments

@joaopaulofilho
Copy link

When fetched and synced (my case was production to local) the database were encoded with latin1, although my database was set to utf8_general_ci.

A way to test it should be an database with utf8 enconding.

Just in time: is there a way to set charset enconding on toml's config?

Regards for the great work.

@joaopaulofilho joaopaulofilho changed the title conding issues encoding issues Feb 8, 2017
@timakin
Copy link
Owner

timakin commented Feb 9, 2017

Hi joaopaulofilho, thank you for your question.
That's a kind of critical issue, but so far gopli doesn't have an appropriate solution.
But from this weekend, I'll begin to add stable test code for this project,
and on the process, I'll add an encoding support, other management system like postgresql support and so on.
So just a moment please.
Regards.

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

No branches or pull requests

2 participants