Lists: | pgsql-general |
---|
From: | David Edwards <david(at)omelett(dot)es> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Which locale to use for multiple-language support? |
Date: | 2009-11-09 10:57:08 |
Message-ID: | 608c66280911090257s121a6e43u2feca9687d222c8b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
Hi,
Some of postgresql's string functions behave differently depending on the
locale the cluster was created with. With the locales 'C' or 'en_US.utf8',
lower() does not lowercase non-ascii characters such as Ü (umlaut-u).
If we have users from all over the world storing data in our database with
all sorts of languages, which locale should we use to ensure these string
functions behave as they expect?
Thanks,
--
David Edwards
From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | David Edwards <david(at)omelett(dot)es> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Which locale to use for multiple-language support? |
Date: | 2009-11-09 21:42:15 |
Message-ID: | 1257802935.6507.0.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
On mån, 2009-11-09 at 10:57 +0000, David Edwards wrote:
> If we have users from all over the world storing data in our database
> with all sorts of languages, which locale should we use to ensure
> these string functions behave as they expect?
Try en_US.utf8. It is pretty language neutral.