Gosh, please leave it in it is superb, great, fantastic ... 
If somebody defines a different behavior as standard in the future,
we will need to tell him that he has a gordian knot in his brains :-)

Andreas 

> I understand this. And this is how it works currently:
> 
> select * from tab where (A,B) >= ANY (select X, Y from tab2);
> 
> means: select tuples where A >= X _and_ B >= Y for some tuple from tab2.
>                                   ^^^^^
>          'AND' is used for all Op-s except for '<>' when 'OR' is used.
> 
> Question is "should we drop this feature (?) or leave it as is ?"


Tue, 17 Feb 1998 09:52:50 +0100
Zeugswetter Andreas SARZ <Andreas.Zeugswetter@telecom.at>
Re: Subselects open issue Nr. NEW
> 
> Gosh, please leave it in it is superb, great, fantastic ... 
> If somebody defines a different behavior as standard in the future,
> we will need to tell him that he has a gordian knot in his brains :-)
> 
> Andreas 
> 
> > I understand this. And this is how it works currently:
> > 
> > select * from tab where (A,B) >= ANY (select X, Y from tab2);
> > 
> > means: select tuples where A >= X _and_ B >= Y for some tuple from tab2.
> >                                   ^^^^^
> >          'AND' is used for all Op-s except for '<>' when 'OR' is used.
> > 
> > Question is "should we drop this feature (?) or leave it as is ?"
> 
> 
> 

I think my recent posting answers this.  You have to comare from
left-to-right until you find an answer.

-- 
Bruce Momjian
maillist@candle.pha.pa.us

Tue, 17 Feb 1998 11:02:49 -0500 (EST)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] Re: Subselects open issue Nr. NEW