Re: BUG #5028: CASE returns ELSE value always when type is "char" - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5028: CASE returns ELSE value always when type is "char"
Date
Msg-id 603c8f070909040850o6433dc97o97f60d35e104bc31@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5028: CASE returns ELSE value always when type is "char"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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. =A0So 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. =A0On the whole, throwing an error seems better from a usability
> perspective.

I like errors.

...Robert

pgsql-bugs by date:

Previous
From: "Dennis Seran"
Date:
Subject: BUG #5036: Advisory locks have unexpected behavior
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #5036: Advisory locks have unexpected behavior