Re: Bug #633: CASE statement evaluation does not short-circut

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: colejatmsu(dot)edu(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug #633: CASE statement evaluation does not short-circut
Date: 2002-04-16 02:33:05
Message-ID: 3CBB8D61.7F2498CA@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

...
> I don't really consider this a bug; at least, fixing it would imply not
> const-simplifying the result expressions of CASEs, which is a cure far
> worse than the disease IMHO. Does anyone think we *should* allow CASE
> to defeat const-simplification?

No. Constant-folding during parsing should *always* be allowed.

- Thomas

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jochem van Dieten 2002-04-16 10:19:12 Re: Alter/update large tables - VERRRY annoying behaviour!
Previous Message Tatsuo Ishii 2002-04-16 01:08:46 Re: oh, i don't know did it is a bug or not.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2002-04-16 02:42:47 Re: regexp character class locale awareness patch
Previous Message Peter Eisentraut 2002-04-16 02:07:11 Re: multibyte support by default