| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org, Inoue(at)tpf(dot)co(dot)jp |
| Subject: | Re: UTF-8 data migration problem in Postgresql 7.2 |
| Date: | 2002-02-20 16:20:43 |
| Message-ID: | 200202201620.g1KGKhFP027071@www1.translationforge |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Dear friends,
> Hard to believe it's a pg_dump bug.
You are right, Yudit shows an invalid UTF-8 character.
For example, record OID 20643 has invalid =E3=82 character. But, when
querying the PostgreSQL 7.1.3 database, I can see the missing character which
displays well in Apache/PHP.
It seems to be a pg_dump bug or a peculiar kind of UTF-8 (is there any
difference between Windows / Unix ?). There are hundreds of errors in the
complete dump. But the data displays always well.
How can I test the database further in psql or in PHP. I would like to query
record OID 20643 and see if E3/82 is there or not. Any idea how to proceed?
Thank you very much for your help.
Best regards,
Jean-Michel POURE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-02-20 16:24:32 | Re: pg_type defaults |
| Previous Message | Stephan Szabo | 2002-02-20 16:02:53 | Re: pg_dump: use ALTER TABLE for PKs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-20 17:04:29 | Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
| Previous Message | Kristis Makris | 2002-02-20 15:36:28 | Re: Are multiple selects of the same field allowed |