Re: BUG #4478: = operator in connection with CASE looks like loose some functionality (bug or feature?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert 'BoBsoN' Partyka" <bobson(at)bobson(dot)pl>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4478: = operator in connection with CASE looks like loose some functionality (bug or feature?)
Date: 2008-10-21 21:08:46
Message-ID: 9231.1224623326@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Robert 'BoBsoN' Partyka" <bobson(at)bobson(dot)pl> writes:
> In construction "... ind = case ..." automagic conversion from text to
> integer is not done anymore in 8.3.* - you must cast it manually.

> Is this bug or feature? (for me it looks like bug).

It's intentional.

> If this is feature then I think it should be documented in manual and
> probably in some migration documentation.

See the first item under the 8.3 migration caveats:
"Non-character data types are no longer automatically cast to TEXT"
http://www.postgresql.org/docs/8.3/static/release-8-3.html

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-10-21 21:10:45 Re: BUG #4481: Big text insert/update using functions failed
Previous Message Joshua Tolley 2008-10-21 20:26:17 Re: BUG #4482: Segfault error 4