| From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
|---|---|
| To: | <pgsql(at)markdilger(dot)com> |
| Cc: | <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <alvherre(at)commandprompt(dot)com>, <kleptog(at)svana(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug in UTF8-Validation Code? |
| Date: | 2007-04-05 09:52:14 |
| Message-ID: | AFCCBB403D7E7A4581E48F20AF3E5DB202088849@EXADV1.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii wrote:
> I think we need to continute design discussion, probably
> targetting for 8.4, not 8.3.
But isn't a simple fix for chr() and ascii(), which does not
require a redesign, a Good Thing for 8.3 if possible? Something
that maintains as much upward and/or Oracle compatibility as
possible while doing away with ascii('EUR') returning 226 in UTF-8?
And I think - correct me if I am wrong - that conversion between
character and integer representation of the character in the current
database encoding is exactly that.
I see Tom Lane's point in rejecting chr(0), though.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stuart Bishop | 2007-04-05 10:23:09 | Re: elog(FATAL) vs shared memory |
| Previous Message | Heikki Linnakangas | 2007-04-05 09:35:33 | Re: Checkpoint gets stuck in mdsync |