| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jm(dot)poure(at)freesurf(dot)fr |
| Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org, Inoue(at)tpf(dot)co(dot)jp |
| Subject: | Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
| Date: | 2002-02-20 17:04:29 |
| Message-ID: | 891.1014224669@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> writes:
> 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.
Does your Apache/PHP environment set any particular client encoding?
I am wondering if Apache is seeing a different translation of the
database contents than what pg_dump got.
BTW, it seems entirely likely that Windows apps might display something
for UTF-8 sequences that are invalid according to the published specs.
It'd be just like Microsoft to "extend" the standard...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-02-20 17:10:38 | Re: pg_type defaults |
| Previous Message | Masaru Sugawara | 2002-02-20 17:02:46 | Re: Trouble with pg_dumpall import with 7.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2002-02-20 17:13:03 | Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
| Previous Message | Jean-Michel POURE | 2002-02-20 16:20:43 | Re: UTF-8 data migration problem in Postgresql 7.2 |