Re: ERROR: FULL JOIN is only supported with merge-joinable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Harco de Hilster <Harco(dot)de(dot)Hilster(at)ATConsultancy(dot)nl>, pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: FULL JOIN is only supported with merge-joinable
Date: 2006-03-13 20:28:13
Message-ID: 9946.1142281693@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> I think you could do something involving a time interval datatype that
>> considers "overlap" as equality and does something reasonable for
>> sorting non-overlapping intervals.

> How could a non-transitive property ever be merge joinable though?

Um, good point. So it couldn't be "overlaps" in the normal sense of the
word. But given that he's mostly concerned about cases where one end is
+infinity, it might be possible to devise a consistent semantics that
works.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Berend Tober 2006-03-13 20:36:28 Re: multi-column aggregates
Previous Message Merlin Moncure 2006-03-13 20:27:43 Re: multi-column aggregates