Horton

Re: Bug in UTF8-Validation Code?

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: Tatsuo Ishii <ishii@postgresql.org>, alvherre@commandprompt.com, pgsql@markdilger.com, all@adv.magwien.gv.at, pgsql-hackers@postgresql.org
Date: 2007-04-05T14:47:18Z
Lists: pgsql-hackers 
Martijn van Oosterhout <kleptog@svana.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