| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
| Subject: | Re: Converting an ASCII database to an UTF-8 database |
| Date: | 2006-02-18 10:06:17 |
| Message-ID: | 200602181106.18338.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rick Gigger wrote:
> I have this exact problem. I have dumped and reloaded other
> databases and set the client encoding to convert them to UTF-8 but I
> have one database with values that still cause it to fail, even if I
> specify that the client encoding is SQL_ASCII. How do I fix that?
Well then you need to figure out what encoding those non-ASCII
characters actually are and set the client encoding to that. Trying
LATIN1 might be a good start, but if you users/applications have
inserted random bytes then you will have to sort it out by hand.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2006-02-18 10:09:51 | Re: TSearch2 / German compound words / UTF-8 |
| Previous Message | Peter Eisentraut | 2006-02-18 10:05:05 | Re: Converting an ASCII database to an UTF-8 database |