Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 63E91477045 for ; Fri, 13 Dec 2002 14:38:09 -0500 (EST) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 2DBB947704E for ; Fri, 13 Dec 2002 14:37:50 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2280396; Fri, 13 Dec 2002 11:38:15 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Ludwig Lim , PostgreSQL Mailing List Subject: Re: A PL/PgSQL Question Date: Fri, 13 Dec 2002 11:41:36 -0800 X-Mailer: KMail [version 1.4] References: <20021213175023.75148.qmail@web80302.mail.yahoo.com> In-Reply-To: <20021213175023.75148.qmail@web80302.mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200212131141.36957.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/184 X-Sequence-Number: 10772 Ludwig, > What is the difference between the first and second > chunk PL/PgSQL INSERT/UPDATE trigger function code > aside from the fact that first scenario will result in > an "ABORT" state? >=20 > Are there any instances where a NOTICE and a RETURN > NULL statement is a much better than a RAISE EXCEPTION > statement? Not that I have encountered, but YMMV. --=20 -Josh Berkus Aglio Database Solutions San Francisco