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

On Fri, Sep 4, 2009 at 11:15 AM, Tom Lane<tgl@sss.pgh.pa.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