Re: orderRules() now a bad idea? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: orderRules() now a bad idea?
Date
Msg-id 6318.1034828476@sss.pgh.pa.us
Whole thread Raw
In response to Re: orderRules() now a bad idea?  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: orderRules() now a bad idea?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: orderRules() now a bad idea?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> It looks like NAME comparison uses strcmp (actually strncmp).  So it'll
>> be numeric byte-code order.
>> There's no particular reason we couldn't make that be strcoll instead,
>> I suppose, except perhaps speed.

> But how will this work when we have per-column/datum collation order?
> And what about languages that don't have any useful collation order for
> their alphabets (far east)?  ISTM that a globally viable feature of this
> sort would have to sort by something numeric.

I'm confused; are you saying that NAME's sort behavior is good as-is?
If not, what would you have it do differently?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PL/Perl and Perl 5.8
Next
From: Gavin Sherry
Date:
Subject: Re: "COPY FROM" recognize \xDD sequence - addition to