From: | raf <raf(at)raf(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: help understanding collation order |
Date: | 2011-01-19 03:15:08 |
Message-ID: | 20110119031507.GA26684@raf.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
raf wrote:
> Peter Eisentraut wrote:
>
> > On tis, 2011-01-18 at 10:33 +1100, raf wrote:
> > > p.s. if anyone in debian locale land is listening,
> > > 'E' does not sort before ','. what were you thinking? :-)
> >
> > What is actually happening is that the punctuation is sorted in a second
> > pass after the letters. Which is both correct according to the relevant
> > standards and also practical in many situations.
>
> i have no doubt that what you say is true just as i have no doubt that
> it is also incorrect and impractical in every situation i'll ever encounter.
> i can't imagine ever wanting CLARK to sort both before and after CLARKE.
> i'll just re-sort all name-ordered reports in the client. pity.
better idea: i'll separate the family name from the personal
names using regexp_replace() and use them separately in the
order by clause so the sorting can remain in postgres where
it belongs without any commas getting in the way.
cheers,
raf
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-01-19 06:09:34 | Re: Another table/column has semi-current COUNTs? |
Previous Message | Ozz Nixon | 2011-01-19 03:06:07 | Another table/column has semi-current COUNTs? |