Re: upper and UTF-8

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(dot)marlowe(at)gmail(dot)com]
> Sent: Monday, July 26, 2010 3:39 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] upper and UTF-8
>
> I'd try creating a db with en_US or even better whatever is spanish
> encoding for lc_collate and see what happens.
>
> On Mon, Jul 26, 2010 at 3:18 PM, Benjamin Krajmalnik
> <kraj(at)servoyant(dot)com> wrote:
> > CREATE DATABASE ishield
> >  WITH OWNER = postgres
> >       ENCODING = 'UTF8'
> >       LC_COLLATE = 'C'
> >       LC_CTYPE = 'C'
> >       CONNECTION LIMIT = -1;
> >
> >
> >> -----Original Message-----
> >> From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
> >> Sent: Monday, July 26, 2010 3:17 PM
> >> To: Benjamin Krajmalnik
> >> Cc: pgsql-admin(at)postgresql(dot)org
> >> Subject: Re: [ADMIN] upper and UTF-8
> >>
> >> On Mon, Jul 26, 2010 at 3:03 PM, Benjamin Krajmalnik
> >> <kraj(at)servoyant(dot)com> 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.
> >
>
>
>
> --
> To understand recursion, one must first understand recursion.