| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, laurenz(dot)albe(at)wien(dot)gv(dot)at, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-11 01:57:43 |
| Message-ID: | 46E5F617.3040807@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tatsuo Ishii wrote:
>
> If you regard the unicode code point as simply a number, why not
> regard the multibyte characters as a number too? I mean, since 0xC2A9
> = 49833, "select chr(49833)" should work fine no?
>
>
No. The number corresponding to a given byte pattern depends on the
endianness of the architecture. That's exactly why we can't sanely use
the byte pattern of the encoded characters as numbers.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2007-09-11 02:27:50 | Re: invalidly encoded strings |
| Previous Message | Tom Lane | 2007-09-11 01:42:10 | Re: invalidly encoded strings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-11 02:11:04 | Re: HOT patch - version 15 |
| Previous Message | Tom Lane | 2007-09-11 01:42:10 | Re: invalidly encoded strings |