From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: orderRules() now a bad idea? |
Date: | 2002-10-17 18:54:30 |
Message-ID: | 200210171854.g9HIsUk24204@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)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?
Yes, exotic ordering of rules just doesn't seem warranted. I think it
should match the ordering of pg_class.name, which is strcmp() already.
Let's do ASCII ordering (strcmp) and see how things go.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-10-17 18:55:34 | Re: "COPY FROM" recognize \xDD sequence - addition to |
Previous Message | Teodor Sigaev | 2002-10-17 18:34:50 | Current CVS has strange parser for float type |