Re: Problems importing Unicode - Mailing list pgsql-general

From matthias@cmklein.de
Subject Re: Problems importing Unicode
Date
Msg-id E1CUHfY-0002AK-00@www.strato-webmail.de
Whole thread Raw
In response to Problems importing Unicode  (matthias@cmklein.de)
Responses Re: Problems importing Unicode
List pgsql-general
Well, they were generated by MySQL and I can open them with e.g. the
Windows Editor Notepad. But I don't know if they are actually encoded in
UNICODE.
Since I can open the file with Notepad and read the statements, I assume,
it is not UNICODE. They look just like in the email below.

The problem are apparently those characters Å or ô and I really would like
to know how to import those files into PostgreSQL 8.0.0

Is there a switch I can use to do a codepage / encoding translation?

Why are MS Access or even MySQL able to read those files without trouble
but PostgreSQL reports an error?

Thanks

Matt



--- Ursprüngliche Nachricht ---
Datum: 17.11.2004 02:25
Von: Tatsuo Ishii <t-ishii@sra.co.jp>
An: matthias@cmklein.de
Betreff: Re: [GENERAL] Problems importing Unicode

> > I have batch files with entries such as
> >
> > INSERT INTO country VALUES (248,'ALA','AX','Åland Islands');
> > INSERT INTO country VALUES (384,'CIV','CI','Côte d\'Ivoire');
> >
> > I tried to execute them using "pgsql \i filename.sql"
> >
> > Unfortunately, I keep getting an error message:
> > "ERROR:  invalid byte sequence for encoding "UNICODE": 0xc56c"
> >
> > How can that be possible?
> > My database is set to encoding "UNICODE" and so are the batchfiles.
> >
> > Why does that not work?
>
> I bet your batch file is not encoded in UNICODE (UTF-8).
> --
> Tatsuo Ishii
>


pgsql-general by date:

Previous
From: Marco Bizzarri
Date:
Subject: Certifications in military environment
Next
From: Joel
Date:
Subject: Q about NAS mounting things