X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3FBD2D1B50E for ; Mon, 8 Sep 2003 16:57:37 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 79293-07 for ; Mon, 8 Sep 2003 13:57:06 -0300 (ADT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.189]) by svr1.postgresql.org (Postfix) with ESMTP id BDC6BD1B513 for ; Mon, 8 Sep 2003 13:57:04 -0300 (ADT) Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19wPK1-0003hl-00; Mon, 08 Sep 2003 18:57:01 +0200 Received: from [80.129.141.206] (helo=pse-consulting.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19wPK1-0003OC-00; Mon, 08 Sep 2003 18:57:01 +0200 Message-ID: <3F5CB4E2.70506@pse-consulting.de> Date: Mon, 08 Sep 2003 18:57:06 +0200 From: Andreas Pflug User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Doug McNaught , pgsql-hackers@postgresql.org Subject: Re: plpgsql doesn't coerce boolean expressions to boolean References: <15403.1063035632@sss.pgh.pa.us> <3F5CAC68.30502@pse-consulting.de> <19042.1063039625@sss.pgh.pa.us> In-Reply-To: <19042.1063039625@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/560 X-Sequence-Number: 43572 Tom Lane wrote: >Doug McNaught 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? > Good question. A NOTICE just might be ignored, breaking everything "surprisingly" in 7.5. To speak a bit more general, how about some sort of "deprecation checker" setting, if set to true anything marked as deprecated will throw an error, if false only a notice will be generated. This would enable users to check their existing stuff for future compatibility before it's broken in the next release. Regards, Andreas