2010/6/4 Wang, Mary Y :
> Hi,
>
> I'm getting this error from postgres " ERROR: character 0x90 of encoding
> "WIN1252" has no equivalent in "UTF8" " and from a dump file when I tried to
> use psql command to restore the dump.
>
> I have SET client_encoding = 'win1252' in the dump file.
>
> Any
On Saturday 05 June 2010 7:07:35 am Wang, Mary Y wrote:
> Thanks Alban, but I'm still confused.
> I just read the PostgreSQL manual, and got the impression that UTF8 would
> take care of ALL character sets, so I put SET client_encoding = 'UTF8' in
> the dump file, and reload it again, then I got ev
ent.utwente.nl]
> Sent: Saturday, June 05, 2010 1:35 AM
> To: Wang, Mary Y
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] ERROR: character 0x90 of encoding "WIN1252" has no
> equivalent in "UTF8"
>
> On 5 Jun 2010, at 4:44, Wang, Mary Y wrot
uggestions?
Thanks
Mary
-Original Message-
From: Alban Hertroys [mailto:dal...@solfertje.student.utwente.nl]
Sent: Saturday, June 05, 2010 1:35 AM
To: Wang, Mary Y
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] ERROR: character 0x90 of encoding "WIN1252" has no
equiv
On 5 Jun 2010, at 4:44, Wang, Mary Y wrote:
> Hi,
>
> I'm getting this error from postgres " ERROR: character 0x90 of encoding
> "WIN1252" has no equivalent in "UTF8" " and from a dump file when I tried to
> use psql command to restore the dump.
>
> I have SET client_encoding = 'win1252' in
Hi,
I'm getting this error from postgres " ERROR: character 0x90 of encoding
"WIN1252" has no equivalent in "UTF8" " and from a dump file when I tried to
use psql command to restore the dump.
I have SET client_encoding = 'win1252' in the dump file.
Any ideas?
Thanks
Mary
--
Sent via p
