Re: Patch for collation using ICU

From: "John Hansen" <john(at)geeknet(dot)com(dot)au>
To: "Palle Girgensohn" <girgen(at)pingpong(dot)net>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for collation using ICU
Date: 2005-05-07 12:22:52
Message-ID: 5066E5A966339E42AA04BA10BA706AE50A92FB@rodrick.geeknet.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> I use this patch in production on one FreeBSD 4.10 server at
> the moment.
> With the latest version, I've had no problems. Logging is
> swithed on for
> now, and it shows no signs of ICU complaining. I'd like more
> reports on
> Linux, though.

I currently use this on gentoo with ICU3.2 unmasked.

Works a dream, even with locale C and UNICODE database.

Small test:

createdb --encoding UNICODE --locale C test
psql test
set client_encoding=iso88591;
CREATE TABLE test (t text);
INSERT INTO test (t) VALUES ('æøå');
set client_encoding=unicode;
INSERT INTO test (t) SELECT upper(t) FROM test;
set client_encoding=iso88591;
SELECT * FROM test;
t
-----
æøå
ÆØÅ
(2 rows)

Just as I'd expect, as upper/lower/initcap are locale independent for these characters.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message apoc9009@yahoo.de 2005-05-07 12:30:43
Previous Message Palle Girgensohn 2005-05-07 12:07:34 Re: Patch for collation using ICU