Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Removing SORTFUNC_LT/REVLT


  • From: Martijn van Oosterhout <kleptog@svana.org>
  • To: Tom Lane <tgl@sss.pgh.pa.us>
  • Cc: pgsql-hackers@postgresql.org
  • Subject: Re: Removing SORTFUNC_LT/REVLT
  • Date: Fri, 30 Dec 2005 16:07:25 +0100
  • Message-id: <20051230150725.GE15410@svana.org>

On Thu, Dec 29, 2005 at 10:49:23AM -0500, Tom Lane wrote:
> What I'd really like is to deprecate the "USING operator" syntax in
> favor of a "USING operatorclassname" syntax.  Actually, "USING opclass
> [ASC/DESC]" would get the job done, since given an opclass you can
> certainly run the sort function either normal or reverse.

Thought of something this morning: this seems OK at first glance but I
don't think it's workable. The example being locale dependant sorting.
I really don't think we want to create a new operator class for each
possible way you can sort strings.

Collations (currently anyway) are really just an operator class +
[ASC/DESC] + optional locale rolled into a single identifier. The idea
being that when you use '<', the collation on that node decides
unambiguously which version of '<' you mean, rather than looking up the
operator and trying to guess which operator class you meant.

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

Attachment: pgpNWc6vlGzBp.pgp
Description: PGP signature



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group