On Wed, Jan 18, 2017 at 7:00 PM, Andres Freund <and...@anarazel.de> wrote: >>So, one of the big reasons I use CASE is to avoid evaluating >>expressions in cases where they might throw an ERROR. Like, you know: >> >>CASE WHEN d != 0 THEN n / d ELSE NULL END >> >>I guess it's not the end of the world if that only works for >>non-set-returning functions, but it's something to think about. > > That's already not reliable in a bunch of cases, particularly evaluation > during planning... Not saying that's good, but it is.
Whee! :-) -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
