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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5028: CASE returns ELSE value always when type is "char"
Date: 2009-09-04 15:50:25
Message-ID: 603c8f070909040850o6433dc97o97f60d35e104bc31@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Sep 4, 2009 at 11:15 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I certainly don't want to have "char" emulate the misbegotten decision
> to have explicit and implicit coercions behave differently.  So it
> looks to me like the argument to make "char" work like char(1) doesn't
> actually help us much to decide if an error should be thrown here or
> not.  On the whole, throwing an error seems better from a usability
> perspective.

I like errors.

...Robert

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2009-09-04 15:50:55 Re: BUG #5036: Advisory locks have unexpected behavior
Previous Message Tom Lane 2009-09-04 15:15:21 Re: BUG #5028: CASE returns ELSE value always when type is "char"