Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE

Chris BSomething <xpusostomos@gmail.com>

From: Chris BSomething <xpusostomos@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>
Date: 2025-02-17T23:39:31Z
Lists: pgsql-bugs
On Tue, Feb 18, 2025, 7:13 AM David G. Johnston <david.g.johnston@gmail.com>
wrote:

> On Mon, Feb 17, 2025 at 3:49 PM Chris BSomething <xpusostomos@gmail.com>
> wrote:
>
>> That sounds like a lot of words to justify an error that could be caught
>> at parse time, that is actually never caught at all.  It seems to me that
>> whatever type is inferred from a long constant string, it won't fit into a
>> char... At least not without casting it. And therefore an error should come
>> out.
>>
>
> I thought you were trying to convince people to modify the documentation?
> This reads more like wanting to hack the parser to teach it forbidden
> knowledge.
>

Hack? Forbidden knowledge? What an odd comment.



>
>