From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | alvarezp(at)octavio(dot)ods(dot)org |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: LC_COLLATE=es_MX in PgSQL 7.3.2 |
Date: | 2003-06-12 04:19:47 |
Message-ID: | 26426.1055391587@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Octavio Alvarez" <alvarezp(at)octavio(dot)ods(dot)org> writes:
> Ohh! Look at this... I think query #4 does not handle the accents
> correctly, and it should behave almost like #5 does, except for the record
> with p = 'R' which should be at the top (if they were #4's results).
> I'm using PGSQL 7.3.2 under Redhat Linux 8.0. The database was initialized
> with --lc-collate=es_MX.
How about --lc-ctype? I think that accent handling would be driven by
LC_CTYPE not LC_COLLATE. In any case, this is not a Postgres bug unless
you can show that other programs using the same LC_foo settings behave
differently. We punt pretty much all locale-related processing to
subroutines in libc.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-06-12 04:32:48 | Re: need a method to ping a running database |
Previous Message | Ang Chin Han | 2003-06-12 04:08:15 | Re: Index not being used in MAX function (7.2.3) |