> AFAICS this ambiguity is built into the SQL standard, and in fact it's > possible to generate cases that are legally parseable either way: > > SELECT foo.x = ANY((SELECT bar.y FROM bar)) FROM foo; > > [...] > > So I think that the SQL committee shot themselves in the foot when they > decided it was a good idea to call the boolean-OR aggregate "ANY", and > our addition of an array option isn't the fundamental problem. > > Anyone know if SQL2003 fixed this silliness?
It does not seemed to be fixed in the copy I found, but it may not be the last version. As a "temporary" fix, what about "_ANY" and "_SOME" as aggregate names? -- Fabien Coelho - [EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
