> AFAICS this ambiguity is built into the SQL standard, and in fact it's
> possible to generate cases that are legally parseable either way:
> SELECT foo.x = ANY((SELECT bar.y FROM bar)) FROM foo;
> So I think that the SQL committee shot themselves in the foot when they
> decided it was a good idea to call the boolean-OR aggregate "ANY", and
> our addition of an array option isn't the fundamental problem.
> Anyone know if SQL2003 fixed this silliness?
It does not seemed to be fixed in the copy I found, but it may not be the
As a "temporary" fix, what about "_ANY" and "_SOME" as aggregate names?
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2004-04-30 16:14:13|
|Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...|
|Previous:||From: Tom Lane||Date: 2004-04-30 16:07:07|
|Subject: Re: pgsql-server/ /configure /configure.in rc/incl ... |