Re: [GENERAL] 9.5 "chained equality" behavior - Mailing list pgsql-general

From David G. Johnston
Subject Re: [GENERAL] 9.5 "chained equality" behavior
Date
Msg-id CAKFQuwai_koXpB_GhTFCTw=YiAHDg9peXOKs7ijT7-N2sVBSbA@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] 9.5 "chained equality" behavior  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On Tue, May 30, 2017 at 2:32 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:
​...​
 namely because aside from equality all of the comparison operators convert their inputs to a boolean and so cannot be placed in sequence like shown here (boolean compared to, say, integer doesn't work). Boolean equality is the one exception which is what no longer works - so the docs are correct.


​Yes, that was poorly written...booleans keep the same type and so can be "chained" while other types do not.  But precedence is not based upon type, just the operator.

David J.​

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [GENERAL] 9.5 "chained equality" behavior
Next
From: Ludovic Vaugeois-Pepin
Date:
Subject: Fwd: [GENERAL] pg_basebackup error: replication slot"pg_basebackup_2194" already exists