Problems with Postgresql (unicode<->sql_ascii)

Next topic

Author	Message
Kai Duebbert	Friday 26 March 2004 2:55:11 am Hi, I'm currently working on a site that uses Chinese and English content on Postgresql. Everything was going fine, but now I wanted to copy the database to a new one. So, I created a new UNICODE database and wanted to input the SQL dump, but got many weird errors. It seems that the database that I used so far was "SQL_ASCII" and not UNICODE how I normally do it. No problems showed and Chinese characters were working. But I can't use the dump to create a new UNICODE database. Does anyone have any suggestions? I want to dump my old database (SQL_ASCII) and input the contents into the new database (UNICODE), but get many "invalid Unicode" errors. Any help appreciated! Kai
George Essig	Friday 26 March 2004 7:54:56 pm This is strictly a PostgreSQL problem. I remember reading a similar question on a PostgreSQL mailing list. See the following thread: http://archives.postgresql.org/pgsql-general/2004-02/msg01192.php George Essig
Kai Duebbert	Saturday 27 March 2004 3:50:23 am Yeah, I know that it's a Postgresql problem (otherwise I would have filed a bug report). But searching the internet didn't show many results. Thanks for your link, I will try it and report if I have success. Kai

Author

Message

Friday 26 March 2004 2:55:11 am

Hi,

I'm currently working on a site that uses Chinese and English content on Postgresql. Everything was going fine, but now I wanted to copy the database to a new one. So, I created a new UNICODE database and wanted to input the SQL dump, but got many weird errors.

It seems that the database that I used so far was "SQL_ASCII" and not UNICODE how I normally do it. No problems showed and Chinese characters were working. But I can't use the dump to create a new UNICODE database.

Does anyone have any suggestions? I want to dump my old database (SQL_ASCII) and input the contents into the new database (UNICODE), but get many "invalid Unicode" errors.

Any help appreciated!

Kai

George Essig

Friday 26 March 2004 7:54:56 pm

This is strictly a PostgreSQL problem. I remember reading a similar question on a PostgreSQL mailing list. See the following thread:

http://archives.postgresql.org/pgsql-general/2004-02/msg01192.php

George Essig

Kai Duebbert

Saturday 27 March 2004 3:50:23 am

Yeah, I know that it's a Postgresql problem (otherwise I would have filed a bug report). But searching the internet didn't show many results.

Thanks for your link, I will try it and report if I have success.

Kai