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

From Andrew Dunstan
Subject Re: plpgsql doesn't coerce boolean expressions to boolean
Date
Msg-id 3F5CC9FE.5030103@dunslane.net
Whole thread Raw
In response to Re: plpgsql doesn't coerce boolean expressions to boolean  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: plpgsql doesn't coerce boolean expressions to boolean  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

>Doug McNaught <doug@mcnaught.org> writes:
>  
>
>>I agree with another poster that deprecation in 7.4 and removal in
>>7.5 might make sense.
>>    
>>
>
>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.

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

cheers

andrew



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: row level lock and table level locks
Next
From: Neil Conway
Date:
Subject: Re: [PATCHES] mcxt.c