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

From Zeugswetter Andreas SARZ
Subject Re: Subselects open issue Nr. NEW
Date
Msg-id 219F68D65015D011A8E000006F8590C6010A51DB@sdexcsrv1.sd.spardat.at
Whole thread Raw
In response to Subselects open issue Nr. NEW  ("Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>)
Responses Re: [HACKERS] Re: Subselects open issue Nr. NEW  (Bruce Momjian <maillist@candle.pha.pa.us>)
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 ?"


pgsql-hackers by date:

Previous
From: "Vadim B. Mikheev"
Date:
Subject: Re: [HACKERS] Re: [BUGS] General Bug Report: palloc fails with lots of ANDs and ORs
Next
From: Zeugswetter Andreas SARZ
Date:
Subject: Re: Subselects open issue Nr. NEW