Skip site navigation (1) Skip section navigation (2)

Re: incorrect collation order in at least some non-C locales

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Martin Pitt <martin(at)piware(dot)de>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>,fgaroso <fgaroso(at)ig(dot)com(dot)br>
Subject: Re: incorrect collation order in at least some non-C locales
Date: 2006-02-05 19:27:44
Message-ID: 20060205112514.N29601@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Sun, 5 Feb 2006, Martin Pitt wrote:

> Hi PostgreSQL developers!
>
> I recently got the email below and confirmed that I get the same
> broken collation order in de_DE.UTF-8 as the original reporter (who
> probably uses pt_PT.something). It works fine in C, though.

This is probably not "broken collation order" but instead how those
locales are defined. Many natural language locales are defined to not use
spaces in first pass ordering (like the ordering in a dictionary). Thus
the first pass strings are effectively, "SUEKO", "SUEE" and "SUET".

> System: Debian unstable, according to the reporter the bug does not
> happen under Windows.

The reason for that is that he has "C" locale under Windows.

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-02-05 19:49:56
Subject: Re: incorrect collation order in at least some non-C locales
Previous:From: Martin PittDate: 2006-02-05 12:56:55
Subject: incorrect collation order in at least some non-C locales

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group