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

Re: pg ANY/SOME ambiguity wrt sql standard?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>,PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg ANY/SOME ambiguity wrt sql standard?
Date: 2004-05-01 01:17:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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.


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 -
PostgreSQL Replicator -- production quality replication for PostgreSQL

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-05-01 01:18:16
Subject: Re: pgsql-server/ /configure / rc/incl ...
Previous:From: Joshua D. DrakeDate: 2004-05-01 01:16:30
Subject: Re: Plan for feature freeze?

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