Re: [HACKERS] Re: Subselects open issue Nr. NEW - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Re: Subselects open issue Nr. NEW
Date
Msg-id 199802171602.LAA25539@candle.pha.pa.us
Whole thread Raw
In response to Re: Subselects open issue Nr. NEW  (Zeugswetter Andreas SARZ <Andreas.Zeugswetter@telecom.at>)
List pgsql-hackers
>
> 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

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Subselects and NOTs
Next
From: Zeugswetter Andreas SARZ
Date:
Subject: AW: [HACKERS] Re: Subselects open issue Nr. NEW