Re: plpgsql doesn't coerce boolean expressions to boolean - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plpgsql doesn't coerce boolean expressions to boolean
Date
Msg-id 453.1063052918@sss.pgh.pa.us
Whole thread Raw
In response to Re: plpgsql doesn't coerce boolean expressions to boolean  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: plpgsql doesn't coerce boolean expressions to boolean  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> How would we "deprecate" it exactly?  Throw a NOTICE?
>> 
> Release notes, I guess. A NOTICE would be fine as long as it didn't 
> result in a flood of them. If that happened once at parse time that 
> should be fine, I think.

It would be relatively difficult to do that; given the way plpgsql is
structured, a runtime message would be a lot easier.

> What's the practice in deprecating other "features"?

We generally don't ;-).  Certainly 7.4 contains bigger incompatible
changes than this one, and so have most of our prior releases.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pgsql vc++|win32
Next
From: Tom Lane
Date:
Subject: Re: constraint modification on todo list