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

Re: pg ANY/SOME ambiguity wrt sql standard?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg ANY/SOME ambiguity wrt sql standard?
Date: 2004-05-01 00:56:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
> As a "temporary" fix, what about "_ANY" and "_SOME" as aggregate names?

Ick :-(.  The use of leading underscores is an ugly C-ism that we should
not propagate into SQL names.

How about bool_or() and bool_and()?  Or at least something based on OR
and AND?  I don't find ANY/ALL to be particularly mnemonic for this
usage anyway.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2004-05-01 01:04:54
Subject: Re: pgsql-server/ /configure / rc/incl ...
Previous:From: Tatsuo IshiiDate: 2004-05-01 00:53:50
Subject: Re: Plan for feature freeze?

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