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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: Martin Pitt <martin(at)piware(dot)de>, 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:49:56
Message-ID: 12508.1139168996@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> This is probably not "broken collation order" but instead how those
> locales are defined.

I'd only consider it "broken" if you get different sort order from
sort(1) under the same locale.  Here is an example from Fedora 4
showing that sort(1) has the same ideas about what de_DE sort order
is:

[tgl ~]$ cat zzz
SUEKO
SUE E
SUE T
[tgl ~]$ sort zzz
SUE E
SUE T
SUEKO
[tgl ~]$ LANG=de_DE.utf8 sort zzz
SUE E
SUEKO
SUE T
[tgl ~]$ 

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: alexisDate: 2006-02-05 19:57:56
Subject: Re: BUG #2237: SELECT optimizer drops everything improperly
Previous:From: Stephan SzaboDate: 2006-02-05 19:27:44
Subject: Re: incorrect collation order in at least some non-C locales

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