Re: [GENERAL] ERROR: FULL JOIN is only supported with merge-joinable join conditions

2006-03-16 Thread Stephen Frost
* Harco de Hilster ([EMAIL PROTECTED]) wrote: > ERROR: FULL JOIN is only supported with merge-joinable join conditions I'm not a big fan of that error either, honestly. > select * > from A > full outer join B on A.f1 = B.f1 and ((A.ExpTime IS NULL AND B.ExpTime > IS NULL) OR (A.ModTime <= B.E

[GENERAL] ERROR: FULL JOIN is only supported with merge-joinable join conditions

2006-03-15 Thread Harco de Hilster
Hi all, I am porting my application from Ingres to Postgres, and I have the following problem. I am not sure if this is a known limitation of Postgresql or a bug. My code works under Ingres but fails in Postgres with the following error: ERROR: FULL JOIN is only supported with merge-joinabl

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

2006-03-13 Thread Greg Stark
Tom Lane <[EMAIL PROTECTED]> writes: > Harco de Hilster <[EMAIL PROTECTED]> writes: > > What is the definition of a merge-joinable condition? > > Equality on a sortable datatype. > > > Can I create an type/operator that compares both records that is > > considered merge-joinable? > > I think y

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

2006-03-13 Thread Tom Lane
Greg Stark <[EMAIL PROTECTED]> writes: > Tom Lane <[EMAIL PROTECTED]> 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

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

2006-03-13 Thread Tom Lane
Harco de Hilster <[EMAIL PROTECTED]> writes: > What is the definition of a merge-joinable condition? Equality on a sortable datatype. > Can I create an type/operator that compares both records that is > considered merge-joinable? I think you could do something involving a time interval datatype

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

2006-03-13 Thread Harco de Hilster
Thanks for your thoughts. What is the definition of a merge-joinable condition? Even if I put ExpTime = Infinity (I saw that one coming ;-)), the same error is reported. My only option here is to add A.exptime = B.exptime (which is only true for live data if I use INFINITY), and lose the abil

Re: [GENERAL] ERROR: FULL JOIN is only supported with merge-joinable join conditions

2006-03-13 Thread Tom Lane
Martijn van Oosterhout writes: > I think the reason it hasn't been done for general join conditions is > because we havn't thought of an efficient algorithm. Right, it's keeping track of the unmatched right-hand rows that's a problem. > However, I wonder if youre case couldn't be handled with a

Re: [GENERAL] ERROR: FULL JOIN is only supported with merge-joinable join conditions

2006-03-13 Thread Martijn van Oosterhout
On Mon, Mar 13, 2006 at 11:02:35AM +0100, Harco de Hilster wrote: > Hi all, > > I am porting my application from Ingres to Postgres, and I have the > following problem. I am not sure if this is a known limitation of > Postgresql or a bug. My code works under Ingres but fails in Postgres > with the

[GENERAL] ERROR: FULL JOIN is only supported with merge-joinable join conditions

2006-03-13 Thread Harco de Hilster
Hi all, I am porting my application from Ingres to Postgres, and I have the following problem. I am not sure if this is a known limitation of Postgresql or a bug. My code works under Ingres but fails in Postgres with the following error: ERROR: FULL JOIN is only supported with merge-joinable jo