peter at pajamian.dhs.org
Thu Dec 4 00:29:40 UTC 2008
On 12/03/2008 04:17 PM, Jon Jensen wrote:
> On Wed, 3 Dec 2008, Peter wrote:
>> That said, the standard way that I usually convert the DB to UTF8 when
>> upgrading is to dump the old database to a text file, then go through
>> and search and replace to change all the encodings from latin1 to utf8.
>> Then you can import and it should be fine.
> By "search and replace" I hope you mean something like iconv or another
> automated encoding conversion tool. :)
ummmm ... yeah ... that's what I meant ::wink:: ::wink::.
It would be nice if pgdump had an option to automatically dump to a
different encoding that you specify, but I'm not aware of one.
> And don't forget to change any encoding declaration in the file itself
> before importing.
Yes, that's what I really meant, heh, but you're right, the encoding
needs to be converted with iconv as well.
More information about the interchange-users