From: Andrew Dunstan <andrew@dunslane.net>
To: Postgresql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: plpgsql doesn't coerce boolean expressions to boolean
Date: Mon, 08 Sep 2003 14:27:10 -0400
Message-ID: <3F5CC9FE.5030103@dunslane.net> (raw)
In-Reply-To: <19042.1063039625@sss.pgh.pa.us>
References: <15403.1063035632@sss.pgh.pa.us>
<3F5CAC68.30502@pse-consulting.de>
<m3d6eb1bmu.fsf@varsoon.wireboard.com>
<19042.1063039625@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: andrew@dunslane.net, pgsql-hackers@postgresql.org
Subject: Re: plpgsql doesn't coerce boolean expressions to boolean
In-Reply-To: <3F5CC9FE.5030103@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox