Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 8A5FD632B89 for ; Mon, 26 Jul 2010 18:47:22 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 87385-06 for ; Mon, 26 Jul 2010 21:47:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.illumen.com (unknown [64.207.29.137]) by mail.postgresql.org (Postfix) with ESMTP id C15CB632B4E for ; Mon, 26 Jul 2010 18:47:14 -0300 (ADT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: upper and UTF-8 Date: Mon, 26 Jul 2010 15:47:13 -0600 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] upper and UTF-8 Thread-Index: AcstCvyAM9RCFW7tRjeAPX5c8GcyiQAAIsXQ References: From: "Benjamin Krajmalnik" To: "Scott Marlowe" Cc: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.107 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RDNS_NONE=0.793 X-Spam-Level: X-Archive-Number: 201007/178 X-Sequence-Number: 35197 Unfortunately, the database has to accept data in multiple languages, = since it is a SaaS offering. It is not a big deal - I just found it interesting that it did not = uppercase the accented letters. The reason I came across it is that I created a table of all the ISO = countries. I had found a NySQL script which created it, and it had the = fields in both upper case and mixed case. Since our platform is = multi-lingual, we expanded the table to add the language code and = started adding the translation. After I finished the translation, I = figured for consistency I would upper case the one field into the other, = and this is where I saw the inconsistency. Operationally, it does not affect me in any way - but I found it strange = that it did not handle the accented characters. For now we are keeping the column to facilitate the translation to other = languages - ultimately it will be dropped. > -----Original Message----- > From: Scott Marlowe [mailto:scott.marlowe@gmail.com] > Sent: Monday, July 26, 2010 3:39 PM > To: Benjamin Krajmalnik > Cc: pgsql-admin@postgresql.org > Subject: Re: [ADMIN] upper and UTF-8 >=20 > I'd try creating a db with en_US or even better whatever is spanish > encoding for lc_collate and see what happens. >=20 > On Mon, Jul 26, 2010 at 3:18 PM, Benjamin Krajmalnik > wrote: > > CREATE DATABASE ishield > > =A0WITH OWNER =3D postgres > > =A0 =A0 =A0 ENCODING =3D 'UTF8' > > =A0 =A0 =A0 LC_COLLATE =3D 'C' > > =A0 =A0 =A0 LC_CTYPE =3D 'C' > > =A0 =A0 =A0 CONNECTION LIMIT =3D -1; > > > > > >> -----Original Message----- > >> From: Scott Marlowe [mailto:scott.marlowe@gmail.com] > >> Sent: Monday, July 26, 2010 3:17 PM > >> To: Benjamin Krajmalnik > >> Cc: pgsql-admin@postgresql.org > >> Subject: Re: [ADMIN] upper and UTF-8 > >> > >> On Mon, Jul 26, 2010 at 3:03 PM, Benjamin Krajmalnik > >> wrote: > >> > I just used the upper(text) function on a database which is utf8 > >> encoded and > >> > which has spanish text. > >> > > >> > All of the regular characters were properly converted, except for > >> characters > >> > which had accents. > >> > >> What are your various LC_* variables for that database? > >> > >> -- > >> To understand recursion, one must first understand recursion. > > >=20 >=20 >=20 > -- > To understand recursion, one must first understand recursion.