From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, john(at)geeknet(dot)com(dot)au, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [PATCHES] UNICODE characters above 0x10000 |
Date: | 2004-08-08 00:14:33 |
Message-ID: | 41157069.1080508@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> If I understood what I was reading, this would take several things:
> * Remove the "special UTF-8 check" in pg_verifymbstr;
> * Extend pg_utf2wchar_with_len and pg_utf_mblen to handle the 4-byte case;
> * Set maxmblen to 4 in the pg_wchar_table[] entry for UTF-8.
>
> Are there any other places that would have to change? Would this break
> anything? The testing aspect is what's bothering me at the moment.
Does this change what client_encoding = UNICODE might produce? The JDBC
driver will need some tweaking to handle this -- Java uses UTF-16
internally and I think some supplementary character (?) scheme for
values above 0xffff as of JDK 1.5.
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-08 00:24:22 | Re: [PATCHES] UNICODE characters above 0x10000 |
Previous Message | Bruce Momjian | 2004-08-08 00:10:07 | Re: parameter hints to the optimizer |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-08-08 00:18:46 | Re: PITR on Win32 - Archive and Restore |
Previous Message | Bruce Momjian | 2004-08-08 00:09:13 | Re: Patch for Array min() / max() |