From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: order by, for custom types |
Date: | 2005-11-19 03:33:38 |
Message-ID: | 16789.1132371218@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> writes:
> Wildcards cause things not to work as they should
> consider everything in [] brackets to be a possible choice and those
> three:
> a = 1.2.3.4
> b = 1.[2,3].3.4
> c = 1.3.3.4
> a = b, b = c, but a <> c, I was told that because of that btree won't
> work on my type. (on irc, that was AndrewSN as I recall).
Well, neither will sorting then. If you can define a consistent sort
order, btree will work; if you can't, then you can't sort either.
AFAICS, with rules like the above you can't define a consistent <
operator.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2005-11-19 05:35:03 | Re: Some array semantics issues |
Previous Message | Bruce Momjian | 2005-11-19 02:17:02 | Re: someone working to add merge? |