Postgres Pro
Downloads
Home   >   mailing lists

Re: pg ANY/SOME ambiguity wrt sql standard? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg ANY/SOME ambiguity wrt sql standard?
Date
Msg-id 8707.1083373014@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg ANY/SOME ambiguity wrt sql standard?  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: pg ANY/SOME ambiguity wrt sql standard?  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: pg ANY/SOME ambiguity wrt sql standard?  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Tree view 
Fabien COELHO <coelho@cri.ensmp.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

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Plan for feature freeze?
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Plan for feature freeze?