Errm,... initdb --encoding UNICODE --locale C > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Hansen > Sent: Saturday, May 07, 2005 10:23 PM > To: Palle Girgensohn; Bruce Momjian > Cc: pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] Patch for collation using ICU > > > > > 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. > > > ---------------------------(end of > broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > >
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
