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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Chris BSomething <xpusostomos(at)gmail(dot)com>
Cc: PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
Date: 2025-02-17 23:12:39
Message-ID: CAKFQuwYALVCQARQ5cELTWzzNpSj56sJ3NehGL_P3iRMs0-grtQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Feb 17, 2025 at 3:49 PM Chris BSomething <xpusostomos(at)gmail(dot)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.

In any case I think this email report is closed and burying any discussion
about this material here just makes it harder for people to find.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-02-17 23:37:56 Re: BUG #18815: Logical replication worker Segmentation fault
Previous Message Chris BSomething 2025-02-17 22:49:40 Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE