| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, alvherre(at)commandprompt(dot)com, pgsql(at)markdilger(dot)com, all(at)adv(dot)magwien(dot)gv(dot)at, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug in UTF8-Validation Code? |
| Date: | 2007-04-05 14:47:18 |
| Message-ID: | 27120.1175784438@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> I think the problem is that most encodings do not have the concept of a
> code point anyway, so implementing it for them is fairly useless.
Yeah. I'm beginning to think that the right thing to do is
(a) make chr/ascii do the same thing as Oracle (ie, as in the discussed
patch)
(b) make a different pair of functions that translate Unicode code
points to/from the current database encoding.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2007-04-05 15:15:42 | Re: Auto Partitioning |
| Previous Message | Tom Lane | 2007-04-05 14:39:38 | Re: Checkpoint gets stuck in mdsync |