Re: UNICODE characters above 0x10000

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "John Hansen" <john(at)geeknet(dot)com(dot)au>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: UNICODE characters above 0x10000
Date: 2004-08-06 18:36:57
Message-ID: 22427.1091817417@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"John Hansen" <john(at)geeknet(dot)com(dot)au> writes:
> Attached, as promised, small patch removing the limitation, adding
> correct utf8 validation.

Surely this is badly broken --- it will happily access data outside the
bounds of the given string. Also, doesn't pg_mblen already know the
length rules for UTF8? Why are you duplicating that knowledge?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2004-08-06 18:51:11 Re: CVS comment
Previous Message Tom Lane 2004-08-06 18:27:45 That dump-comments-on-composite-type-columns patch...

Browse pgsql-patches by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2004-08-06 19:55:28 psql - missing tab-completion support for tablespaces
Previous Message Tom Lane 2004-08-06 18:27:45 That dump-comments-on-composite-type-columns patch...