Re: BUG #13289: ANY() function produces a paradox - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13289: ANY() function produces a paradox
Date
Msg-id CAKFQuwYYLchC22Pkh6kQLkBqYL-Y+Aaf3sNUszEdu75K8Yvuig@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13289: ANY() function produces a paradox  (Anton Pavlov <udtelco@gmail.com>)
List pgsql-bugs
On Fri, May 15, 2015 at 11:06 AM, Anton Pavlov <udtelco@gmail.com> wrote:

> I understand now - thank you. It still rubs me the wrong way that both a
> OP b and a not OP b can be equal - STL would go berserk. I guess it was n=
ot
> so clear to me that ANY / ALL aren't pure functions, more of a control
> structure .
>

=E2=80=8BA "pure" function would have to be able to be used by itself - but=
 the
following gives a syntax error:

SELECT any('{1,2}'::int[])=E2=80=8B

=E2=80=8B
=E2=80=8BDavid J.=E2=80=8B

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #13295: help
Next
From: Evan Martin
Date:
Subject: Re: BUG #13148: Unexpected deferred EXCLUDE constraint violation on derived table