On Sat, 19 May 2001, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > I think what we should probably do is make IN better and use that or then
> > support =ANY(=SOME)/=ALL on such things. I think =ANY would be easy
> > since IN is defined in terms of it in the spec.
>
> And in our code too ;-). ANY/ALL have been there for awhile.
:) Well that makes it easier anyway. I do agree with the point that at
some point IN needs to be smarter. Can the IN always get written as a
join and is it always better to do so?
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
