Re: Reverse-sort indexes and NULLS FIRST/LAST sorting - Mailing list pgsql-hackers

From Michael Glaesemann
Subject Re: Reverse-sort indexes and NULLS FIRST/LAST sorting
Date
Msg-id DBE187F8-A7BD-4058-AE61-07D9C611FDF1@seespotcode.net
Whole thread Raw
In response to Re: Reverse-sort indexes and NULLS FIRST/LAST sorting  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Reverse-sort indexes and NULLS FIRST/LAST sorting  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jan 4, 2007, at 13:33 , Tom Lane wrote:

> Another possible objection is that in the proposed CREATE INDEX syntax
>
>     index-column-id [ opclass-name ] [ DESC ] [ NULLS {FIRST|LAST} ]
>
> DESC must be a fully reserved word else it can't be distinguished from
> an opclass name.  But guess what, it already is.

A point in favor of using DESC over REVERSE as you had earlier  
proposed is that DESC is already a reserved word, while REVERSE isnt'  
even in the list of key words. As DESC is quite closely associated  
with its antonym ASC wrt ordering, any thoughts of allowing ASC as an  
optional noise word? Users may be surprised if ASC were to throw an  
error.

Michael Glaesemann
grzm seespotcode net




pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: -f option for pg_dumpall
Next
From: Dave Page
Date:
Subject: Re: -f option for pg_dumpall