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

Re: problem using twice custom comparision operator

From: Steve Midgley <science(at)misuse(dot)org>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: problem using twice custom comparision operator
Date: 2009-01-25 18:41:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
At 01:20 PM 1/24/2009, pgsql-sql-owner(at)postgresql(dot)org wrote:
>From: Marek Florianczyk <franki(at)adm(dot)tp(dot)pl>
>Organization: TP SA
>To: pgsql-sql(at)postgresql(dot)org
>Subject: problem using twice custom comparision operator
>Date: Fri, 23 Jan 2009 21:42:44 +0100
>Message-Id: <200901232142(dot)44102(dot)franki(at)adm(dot)tp(dot)pl>
>Hi all,
>I wanted to make custom operator to sort data like this:
>in to order:

Hi Marek,

The following idea may be too different to fit your needs, but I got 
some help from this list a while back on how to force sorts for a 
specific query. It sounds like you want to override searching for all 
queries, so this may not be appropriate. Anyway here's an example of a 
solution that sorts things in arbitrary order for any given query:

SELECT * FROM foobar
WHEN 555 then 1
WHEN 342 then 2
WHEN 111 then 3

This sorts "555" then "342" then "111" then everything else.

Obviously this is oversimplified for your case, but you could write 
some comparisons in place of the static numbers (e.g. "555") that 
follow the same rules as the function you're writing. I don't know if 
performance would be anything comparable either (I'd guess that using 
the "regex" operators (like "~*" would be the way to go).

I thought I'd mention this other approach in case it was of interest 
and you haven't run across it before.



pgsql-sql by date

Next:From: Suha OnayDate: 2009-01-26 07:57:07
Subject: Invitation to connect on LinkedIn
Previous:From: Tom LaneDate: 2009-01-23 22:40:52
Subject: Re: problem using twice custom comparision operator

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group