| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Frank Finner <postgresql(at)finner(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org, lloyd(at)middleware-company(dot)com, eric(at)middleware-company(dot)com |
| Subject: | Re: Going from a DB using SQL_ASCII to UNICODE |
| Date: | 2004-04-21 09:51:30 |
| Message-ID: | 200404211151.30593.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 transferring from a different encoding. Please look
> at my statements on the[GENERAL] list for the gory details.
This is not necessary. You just need to set the client encoding correctly
(not SQL_ASCII, but something like LATIN1). The encoding conversion happens
automatically, as usual.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoffrey | 2004-04-21 10:10:04 | Re: unsubscribe |
| Previous Message | Raquel Vieira | 2004-04-21 08:15:28 | unsubscribe |