Re: pg ANY/SOME ambiguity wrt sql standard?

Tom Lane wrote:

>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.
>
>
>
I second this... the whole __ is hard to type and remember.

Sincerely,

Joshua D. Drake

>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
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
>

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL