Tom Lane wrote:I second this... the whole __ is hard to type and remember.Fabien COELHO <[EMAIL PROTECTED]> 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. 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 [EMAIL PROTECTED] -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL |
- [HACKERS] pg ANY/SOME ambiguity wrt sql standard? Fabien COELHO
- Re: [HACKERS] pg ANY/SOME ambiguity wrt sql standard? Fabien COELHO
- Re: [HACKERS] pg ANY/SOME ambiguity wrt sql standard? Tom Lane
- Re: [HACKERS] pg ANY/SOME ambiguity wrt sql stand... Fabien COELHO
- Re: [HACKERS] pg ANY/SOME ambiguity wrt sql s... Tom Lane
- Re: [HACKERS] pg ANY/SOME ambiguity wrt s... Joshua D. Drake
- Re: [HACKERS] pg ANY/SOME ambiguity wrt s... Fabien COELHO
- Re: [HACKERS] pg ANY/SOME ambiguity ... Tom Lane
- Re: [HACKERS] pg ANY/SOME ambigu... Fabien COELHO