Re: pg ANY/SOME ambiguity wrt sql standard?

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg ANY/SOME ambiguity wrt sql standard?
Date: 2004-05-01 09:29:57
Message-ID: Pine.GSO.4.58.0405011127240.6700@chailly99
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > 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.

Ok.

> 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.

Yep.

The standard "EVERY" is fine for postgres, the issue is only with
ANY/SOME.

Do you think that bool_and should be proposed anyway for homogeneity
with bool_or?

--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeroen T. Vermeulen 2004-05-01 12:34:54 Re: New COPY commands in libpq
Previous Message Tony Reina 2004-05-01 09:25:01 Re: New COPY commands in libpq