Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5D638476A38 for ; Fri, 13 Dec 2002 12:50:18 -0500 (EST) Received: from web80302.mail.yahoo.com (web80302.mail.yahoo.com [66.218.79.18]) by postgresql.org (Postfix) with SMTP id 9F3234761EE for ; Fri, 13 Dec 2002 12:50:17 -0500 (EST) Message-ID: <20021213175023.75148.qmail@web80302.mail.yahoo.com> Received: from [202.78.97.48] by web80302.mail.yahoo.com via HTTP; Fri, 13 Dec 2002 09:50:23 PST Date: Fri, 13 Dec 2002 09:50:23 -0800 (PST) From: Ludwig Lim Subject: A PL/PgSQL Question To: PostgreSQL Mailing List MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/179 X-Sequence-Number: 10767 Hi: I have the following PL/PgSQL code blocks: a) IF (condition) THEN RAISE EXCEPTION ''Cannot Insert''; END IF; b) IF (condition) THEN RAISE NOTICE ''Cannot Insert''; RETURN NULL; END IF; 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? Are there any instances where a NOTICE and a RETURN NULL statement is a much better than a RAISE EXCEPTION statement? Thank you very much, ludwig lim __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com