X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id EBE3A9F9F66 for ; Thu, 17 Aug 2006 13:15:12 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 40405-01 for ; Thu, 17 Aug 2006 13:15:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id B88719FA2F3 for ; Thu, 17 Aug 2006 13:15:11 -0300 (ADT) Received: (qmail invoked by alias); 17 Aug 2006 16:15:10 -0000 Received: from dslb-084-063-116-078.pools.arcor-ip.net (EHLO colt.pezone.net) [84.63.116.78] by mail.gmx.net (mp028) with SMTP; 17 Aug 2006 18:15:10 +0200 X-Authenticated: #495269 From: Peter Eisentraut To: pgsql-admin@postgresql.org Subject: Re: RES: Issue on Varchar Ordering Date: Thu, 17 Aug 2006 18:15:08 +0200 User-Agent: KMail/1.9.3 Cc: Erika Terahata Torres Prada e Silva - MPS References: <5519B95F9CA8B94DA8DE3F0A3337567201781A5F@wtdfl055.prevnet> In-Reply-To: <5519B95F9CA8B94DA8DE3F0A3337567201781A5F@wtdfl055.prevnet> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608171815.09141.peter_e@gmx.net> X-Y-GMX-Trusted: 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200608/206 X-Sequence-Number: 22749 Erika Terahata Torres Prada e Silva - MPS wrote: > But it's not correct to my language pt_BR and it worked correctly > with PostgreSQL at Windows and FreeBSD. I have this problem only with > Debian and now I'm looking for some Debian related issue. String ordering is determined by national and international standards. In your case, glibc seems to think that ISO 14651 applies. If you think differently, complain to glibc, or work on changing the standard, or define your own locale. I wouldn't know why Windows and FreeBSD operate differently (I have some idea, but I won't spread rumours). But unless they have a more substantial reason than "We thought this looks reasonable", I'd rather go with the public standard. For that matter, you have not told what you consider the "correct" ordering in your example, nor have you proposed a computation rule to get there. But in the overall scheme of things, first normal form will cooperate better with established sorting rules (for any data type), and vice versa. -- Peter Eisentraut http://developer.postgresql.org/~petere/