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

From Joshua D. Drake
Subject Re: pg ANY/SOME ambiguity wrt sql standard?
Date
Msg-id 4092FA9C.8030007@commandprompt.com
Whole thread Raw
In response to Re: pg ANY/SOME ambiguity wrt sql standard?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:<br /><blockquote cite="mid8707.1083373014@sss.pgh.pa.us" type="cite"><pre wrap="">Fabien COELHO <a
class="moz-txt-link-rfc2396E"href="mailto:coelho@cri.ensmp.fr"><coelho@cri.ensmp.fr></a> writes:
</pre><blockquotetype="cite"><pre wrap="">As a "temporary" fix, what about "_ANY" and "_SOME" as aggregate names?
</pre></blockquote><prewrap="">
 
Ick :-(.  The use of leading underscores is an ugly C-ism that we should
not propagate into SQL names.
 </pre></blockquote> I second this... the whole __ is hard to type and remember.<br /><br /> Sincerely,<br /><br />
JoshuaD. Drake<br /><br /><br /><br /><blockquote cite="mid8707.1083373014@sss.pgh.pa.us" type="cite"><pre wrap="">How
aboutbool_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 <a class="moz-txt-link-abbreviated"
href="mailto:majordomo@postgresql.org">majordomo@postgresql.org</a></pre></blockquote><br /><br /><pre
class="moz-signature"cols="72">-- 
 
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - <a class="moz-txt-link-abbreviated" href="mailto:jd@commandprompt.com">jd@commandprompt.com</a> - <a
class="moz-txt-link-freetext"href="http://www.commandprompt.com">http://www.commandprompt.com</a>
 
PostgreSQL Replicator -- production quality replication for PostgreSQL</pre>

pgsql-hackers by date:

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