Dear Neil,
> As I understand it, there's an ambiguity issue with SOME/ANY, but not
> with EVERY. If so, can we implement EVERY per-spec at least? It's okay
> if we just add EVERY as an alias for BOOL_AND for the sake of homogeneity.
Ok.
> > + /* EVERY aggregate implementation conforming to SQL
Fabien COELHO wrote:
(1) boolean-and and boolean-or aggregates named bool_and and bool_or.
they (SHOULD;-) correspond to standard sql every and some/any aggregates.
they do not have the right name as there is a problem with
the standard and the parser for some/any. Tom also think that
[ Use newest version.]
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Fabien COELHO wro