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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-bugs(at)postgresql(dot)org>,"Sam Mason" <sam(at)samason(dot)me(dot)uk>
Subject: Re: BUG #5028: CASE returns ELSE value always when type is"char"
Date: 2009-09-02 18:27:35
Message-ID: 4A9E72C7020000250002A8F1@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Sam Mason <sam(at)samason(dot)me(dot)uk> wrote:

> you were requiring the types of literals that happened to be
> enclosed in quotes to have their type ascribed, so why not the NULL
> literal?

Well, unless things have changed in recent versions of the standard
and I've missed the change, a series of characters enclosed in
apostrophes is what the standard calls a "character string literal"
and defines it to be be related to character based types such as
varchar. As far as I'm aware, considering it to be undefined is a
PostgreSQL extension. If you can point to something in the standard
to show where I'm mistaken, I'll look it over. I'll go looking for
something to back my memories on the topic, too, since my memory seems
to be less reliable than it once was.....

-Kevin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2009-09-02 18:37:20 Re: BUG #5028: CASE returns ELSE value always when type is"char"
Previous Message Kevin Grittner 2009-09-02 18:21:18 Re: BUG #5028: CASE returns ELSE value always when type is"char"