| From: | jef peeraer <jef(dot)peeraer(at)telenet(dot)be> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Encoding Conversion |
| Date: | 2006-05-09 20:03:13 |
| Message-ID: | 4460F581.6080303@telenet.be |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
beer schreef:
> Hello All
>
> So I have an old database that is ASCII_SQL encoded. For a variety
of reasons I need to convert the database to UNICODE. I did some
googling on this but have yet to find anything that looked like a viable
option, so i thought I'd post to the group and see what sort of advice
might arise. :)
well i recently struggled with the same problem. After a lot of trial
and error and reading, it seems that an ascii encoded database can't use
its client encoding capabilities ( set client_encoding to utf8 ).
i think the easist solution is to do a dump, recreate the database with
a proper encoding, and restore the dump.
jef peeraer
>
> TIA
>
> -b
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Just Someone | 2006-05-09 20:09:35 | Re: A better AND query? |
| Previous Message | Karl O. Pinc | 2006-05-09 19:55:57 | pg_dump design problem (bug??) |