Re: BUG #13289: ANY() function produces a paradox

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Anton Pavlov <udtelco(at)gmail(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13289: ANY() function produces a paradox
Date: 2015-05-15 18:31:25
Message-ID: CAKFQuwYYLchC22Pkh6kQLkBqYL-Y+Aaf3sNUszEdu75K8Yvuig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, May 15, 2015 at 11:06 AM, Anton Pavlov <udtelco(at)gmail(dot)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 not
> so clear to me that ANY / ALL aren't pure functions, more of a control
> structure .
>

​A "pure" function would have to be able to be used by itself - but the
following gives a syntax error:

SELECT any('{1,2}'::int[])​


​David J.​

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Evan Martin 2015-05-17 10:30:07 Re: BUG #13148: Unexpected deferred EXCLUDE constraint violation on derived table
Previous Message Alvaro Herrera 2015-05-15 18:20:01 Re: BUG #13295: help