RE: BUG #15651: Collation setting en_US.utf8 breaking sort order - Mailing list pgsql-bugs

From Daniel Verite
Subject RE: BUG #15651: Collation setting en_US.utf8 breaking sort order
Date
Msg-id 4049e84f-d114-4f48-bec2-432c715e2ff9@manitou-mail.org
Whole thread Raw
In response to RE: BUG #15651: Collation setting en_US.utf8 breaking sort order  (Kaleb Akalework <kaleb.akalework@asg.com>)
List pgsql-bugs
    Kaleb Akalework wrote:

> Ok so if this is intended behavior of UTF8 then I understand. My last
> question then would be if I use a collation setting of C, does it mean I
> won't be able to support multiple languages?

You seem to want to the sort order of C, but be aware that you might
have to decide whether you want this:

=> select upper('é' collate "C");
 upper
-------
 é
(1 row)

or that:

=> select upper('é' collate "en_US");
 upper
-------
 É
(1 row)


To get the sort order of C but the interpretation of characters closer
to what you'd expect from Unicode, it's possible for the database
to have LC_COLLATE to "C", and LC_CTYPE to, say, en_US.UTF-8.
See CREATE DATABASE.


Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite


pgsql-bugs by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: BUG #15651: Collation setting en_US.utf8 breaking sort order
Next
From: PG Bug reporting form
Date:
Subject: BUG #15653: pg_detoast_datum_packed problem