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 <k...@servoyant.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.marl...@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 >> <k...@servoyant.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. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
