Skip site navigation (1) Skip section navigation (2)

Re: pg ANY/SOME ambiguity wrt sql standard?

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg ANY/SOME ambiguity wrt sql standard?
Date: 2004-04-30 16:10:22
Message-ID: Pine.LNX.4.58.0404301808300.25655@sablons.cri.ensmp.fr (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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
last version.

As a "temporary" fix, what about "_ANY" and "_SOME" as aggregate names?

-- 
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-04-30 16:14:13
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
Previous:From: Tom LaneDate: 2004-04-30 16:07:07
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group