X-Original-To: pgsql-patches-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EAA9152B0F for ; Tue, 26 Jul 2005 02:03:50 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 00407-02 for ; Tue, 26 Jul 2005 05:03:46 +0000 (GMT) Received: from mailbox.samurai.com (mailbox.samurai.com [205.207.28.82]) by svr1.postgresql.org (Postfix) with ESMTP id 5F04652ADD for ; Tue, 26 Jul 2005 02:03:45 -0300 (ADT) Received: from localhost (mailbox.samurai.com [205.207.28.82]) by mailbox.samurai.com (Postfix) with ESMTP id 1D90F9B49F; Tue, 26 Jul 2005 01:03:46 -0400 (EDT) Received: from mailbox.samurai.com ([205.207.28.82]) by localhost (mailbox.samurai.com [205.207.28.82]) (amavisd-new, port 10024) with LMTP id 95159-01-10; Tue, 26 Jul 2005 01:03:25 -0400 (EDT) Received: from [61.88.101.19] (unknown [61.88.101.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailbox.samurai.com (Postfix) with ESMTP id 7E9169B49D; Tue, 26 Jul 2005 01:03:24 -0400 (EDT) Message-ID: <42E5C41E.1060805@samurai.com> Date: Tue, 26 Jul 2005 15:03:26 +1000 From: Neil Conway User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pavel Stehule Cc: Bruce Momjian , Tom Lane , pgsql-patches@postgresql.org Subject: Re: User's exception plpgsql References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mailbox.samurai.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.016 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/494 X-Sequence-Number: 16834 Pavel Stehule wrote: > can you show sample, please? modifying_sql_data_not_permitted, null_value_not_allowed, prohibited_sql_statement_attempted and reading_sql_data_not_permitted are the examples I can see from scanning plerrcodes.h. If we had this to do over again, I'm not sure I see the point in mapping a single condition names to multiple SQLSTATEs, but it's probably too late to undo that now. > Exception variables can solve it, but its dead concept. We can have list > of prohibited condition names and for its throw compile error condition > name is ambigous Yeah, that's possible, but it doesn't seem any nicer :-( -Neil