Re: BUG #5028: CASE returns ELSE value always when type is "char"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org, "Sam Mason" <sam(at)samason(dot)me(dot)uk>
Subject: Re: BUG #5028: CASE returns ELSE value always when type is "char"
Date: 2009-09-01 18:42:42
Message-ID: 28785.1251830562@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Joseph Shraibman <jks(at)selectacast(dot)net> writes:
>>> So the type of what is in the ELSE clause determines the type of
>>> the output?
>>
>> If all the other branches are unknown literals, yes.

> What's the best place to look to get a handle on what the benefits are
> of treating character string literals as being of unknown type?
> (Other than the obvious backward compatibility issues.)

I think the odds of changing that are not measurably different from
zero.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2009-09-01 18:49:11 Re: BUG #5028: CASE returns ELSE value always when type is "char"
Previous Message Kevin Grittner 2009-09-01 18:30:13 Re: BUG #5028: CASE returns ELSE value always when type is "char"