Re: plpgsql doesn't coerce boolean expressions to boolean

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql doesn't coerce boolean expressions to boolean
Date: 2003-09-08 18:27:10
Message-ID: 3F5CC9FE.5030103@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

Tom Lane wrote:

>Doug McNaught <doug(at)mcnaught(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2003-09-08 18:32:33 Re: mcxt.c
Previous Message Alvaro Herrera 2003-09-08 18:07:34 Re: row level lock and table level locks

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2003-09-08 20:28:38 Re: plpgsql doesn't coerce boolean expressions to boolean
Previous Message Andreas Pflug 2003-09-08 16:57:06 Re: plpgsql doesn't coerce boolean expressions to boolean