| 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: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
| Date: | 2002-02-22 07:41:12 |
| Message-ID: | 200202220741.g1M7fCFP009096@www1.translationforge |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Le Jeudi 21 Février 2002 05:04, Tatsuo Ishii a écrit :
> o Were server/clien encodings UTF-8 for PostgreSQL?
Yes, I am absolutely sure. Everything from Web page, Apache to PostgreSQL.
> o What are versions of these softwares? Especially of PHP? Is it a
> PHP4? if so, what version? What is the "Php with UTF-8 extensions"?
> I've never heard of it.
PHP 4.06. PHP needs to be compiled with "--enable-mbstring" to allow the
parsing of UTF-8 files and strings. Internal settings set to UTF-8.
I guess the error might come from PostgreSQL string parsing functions:
1) new.target_content:= translate(new.target_content, chr(146), chr (39)) ;
2) substring(text, int4). Is substring multibyte safe?
Cheers,
Jean-Michel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kumar Khare | 2002-02-22 07:43:07 | how to stop running postgres process |
| Previous Message | Bruce Momjian | 2002-02-22 05:52:59 | Re: Solaris ISM Testing |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2002-02-22 09:05:20 | Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
| Previous Message | Jean-Michel POURE | 2002-02-21 22:34:14 | Re: [ODBC] Unicode support |