> > 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 - [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
