| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Neill <rn214(at)hermes(dot)cam(dot)ac(dot)uk> |
| Cc: | rn214(at)cam(dot)ac(dot)uk, PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #1082: Order by doesn't sort correctly. |
| Date: | 2004-02-21 23:25:34 |
| Message-ID: | 13837.1077405934@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Richard Neill <rn214(at)hermes(dot)cam(dot)ac(dot)uk> writes:
> This ordering is perverse!
No kidding.
> No matter what the priority is of the
> different characters, I cannot understand how the above can arise.
You are assuming that it's a byte-at-a-time process. It's not. I
believe the first pass considers only letters and digits.
You can easily prove to yourself that it's not just Postgres. Here's
an example on my Linux laptop:
[tgl(at)g3 tgl]$ cat zzz
Cymbal #1
Cymbal - 18 inch
Cymbal #2
[tgl(at)g3 tgl]$ LC_ALL=C sort zzz
Cymbal #1
Cymbal #2
Cymbal - 18 inch
[tgl(at)g3 tgl]$ LC_ALL=en_GB sort zzz
Cymbal #1
Cymbal - 18 inch
Cymbal #2
[tgl(at)g3 tgl]$
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Damon Hart | 2004-02-22 03:43:36 | intermittent error: 'variable not found in subplan target list' - INCOMPLETE SUBMISSION |
| Previous Message | Richard Neill | 2004-02-21 23:17:33 | Re: BUG #1082: Order by doesn't sort correctly. |