From: | Mike Christensen <mike(at)kitchenpc(dot)com> |
---|---|
To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Easy way to convert a database from WIN1252 to UTF8? |
Date: | 2010-07-01 16:47:03 |
Message-ID: | AANLkTinTxqSlHldnPOsm8MCaWb-wDNNQJOm6k_t2gl7Y@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jul 1, 2010 at 9:44 AM, Sam Mason <sam(at)samason(dot)me(dot)uk> wrote:
> On Thu, Jul 01, 2010 at 09:31:12AM -0700, Mike Christensen wrote:
>> Then, I edited the file in Notepad and saved it as UTF8 which also
>> appears to have worked.
>
> I don't think you want to be doing this. The file should contain a "set
> client_encoding" of the correct value which will let PG to do the "right
> thing" when you import it back into a UTF8 database.
>
> --
> Sam http://samason.me.uk/
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
Yup, that fixed it. I had to change the DB.dbs.out file to use the
new encoding. Duh! Everything's working now.
Mike
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2010-07-01 16:54:21 | Re: Easy way to convert a database from WIN1252 to UTF8? |
Previous Message | Phil Jackson | 2010-07-01 16:46:25 | Cannot open table in new database |