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

use UTF-8 character encoding #145

Open
smrgeoinfo opened this issue Jul 1, 2017 · 2 comments
Open

use UTF-8 character encoding #145

smrgeoinfo opened this issue Jul 1, 2017 · 2 comments
Labels

Comments

@smrgeoinfo
Copy link

When I connect to db using pgAdmin get message:
"The database odm2_db is created to store data using the SQL_ASCII encoding. This encoding is defined for 7 bit characters only; the meaning of characters with the 8th bit set (non-ASCII characters 127-255) is not defined. Consequently, it is not possible for the server to convert the data to other encodings. "

The Earthchem data definitely has some characters that are outside of the 7 bit ascii space. Shouldn't the db use UTF_8. I think this explains why I couldn't use a text pg_dump to restore my EarthChem Db to the Docker container odm2_db-- had to use pg_restore and directory with explicit character encoding parameter.

@lsetiawan lsetiawan added the bug label Jul 11, 2017
@miguelcleon
Copy link
Member

Hmm.. I for sure have non-ASCII characters in my database, @lsetiawan you'll recall this from the WOFpy site error (ODM2/WOFpy#148). Maybe this is caused by the SQL db setup script?

@lsetiawan
Copy link
Member

@miguelcleon Sure enough. Thanks @smrgeoinfo for catching. It seems that the postgresql is defaulting to SQL_ASCII need to change this during the setup.

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

No branches or pull requests

3 participants