BUG #13973: Constants resolved in then/else clauses - Mailing list pgsql-bugs

From harry.townsend@eflowglobal.com
Subject BUG #13973: Constants resolved in then/else clauses
Date
Msg-id 20160218135755.2655.72680@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #13973: Constants resolved in then/else clauses
Re: BUG #13973: Constants resolved in then/else clauses
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      13973
Logged by:          Harry Townsend
Email address:      harry.townsend@eflowglobal.com
PostgreSQL version: 9.1.20
Operating system:   Windows Server 2008
Description:

I attempted to create a safety check in a query using a "case when"
statement such that if the condition evaluated to false, it would return (1
/ 0) in order to nullify the entire transaction. With small conditions, this
works fine. With larger ones, it seems that the constants in the "else"
clause (didn't test for "then" clause) are evaluated before the condition,
causing it to fail every time. If the "else" part requires a column value,
it seems to force the condition to evaluate first though.

pgsql-bugs by date:

Previous
From: zn@dbml.dk
Date:
Subject: BUG #13972: jsonb_to_record cant map camelcase keys
Next
From: Alvaro Herrera
Date:
Subject: Re: aparent bug with pgAdmin version 1.22.1 connected to pg 9.5: SQL Pane view of SEQUENCE object