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 the dump
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 even more errors like:
On 5 Jun 2010, at 16:07, 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 even more
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 even
2010/6/4 Wang, Mary Y mary.y.w...@boeing.com:
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
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
