From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-02 20:46:43 |
Message-ID: | 4A9E9363020000250002A968@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> go with the suggestion of having a character string literal type,
>> and change the semantics such that if there is a valid
>> interpretation of the statement with the character string literal
>> taken as text, it should be used; if not, resolve by current
>> "unknown" rules.
>
> There is already a weak preference for resolving unknown as text in
> the presence of multiple alternatives. So I'm not sure that you're
> suggesting anything different from what happens now.
It is certainly different for the example I gave up-thread involving
"char". Perhaps that is a very unique and isolated situation.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-02 20:55:58 | Re: BUG #5028: CASE returns ELSE value always when type is"char" |
Previous Message | Kevin Grittner | 2009-09-02 20:33:58 | Re: BUG #5028: CASE returns ELSE value always when type is"char" |