Am Dienstag, 20. April 2004 07:05 schrieb Frank Finner:
I answered to a similiar problem on the [GENERAL] list a few days ago. In
short: You can use recode in a pipe between dump and restore like
pg_dump database|recode ascii..utf8|psql newdatabase to get rid of
unicode problems while
hi,
Dion Almaer wrote, On 4/19/2004 21:44:
- ERROR: invalid byte sequence for encoding UNICODE: 0xe9616c
and for this: convert your dump with iconv to unicode, then load it.
C.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet,
Hi -
We are running PostgreSQL 7.1.4, and are finally upgrading... to 7.4.2.
While we do this upgrade, we also want to make create our DB as UNICODE (we
are having problems with SQL_ASCII where we get a bunch of ? marks).
When we try to import the data from a SQL_ASCII dumped db, into the new
Dion Almaer [EMAIL PROTECTED] writes:
When we try to import the data from a SQL_ASCII dumped db, into the new
UNICODE db, everything freaks out.
I'm no expert on this stuff, but I think what you need to do is add
set client_encoding = sql_ascii;
to the top of the dump file. (As of
a DB using SQL_ASCII to UNICODE
Dion Almaer [EMAIL PROTECTED] writes:
When we try to import the data from a SQL_ASCII dumped db, into the
new UNICODE db, everything freaks out.
I'm no expert on this stuff, but I think what you need to do is add
set client_encoding = sql_ascii
Hi,
I answered to a similiar problem on the [GENERAL] list a few days ago. In
short: You can use recode in a pipe between dump and restore like
pg_dump database|recode ascii..utf8|psql newdatabase to get rid of unicode
problems while transferring from a different encoding. Please look at my
