X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 25730D1D298 for ; Fri, 13 Feb 2004 20:29:41 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 23739-06 for ; Fri, 13 Feb 2004 16:29:36 -0400 (AST) Received: from pillette.com (adsl-67-119-5-202.dsl.snfc21.pacbell.net [67.119.5.202]) by svr1.postgresql.org (Postfix) with ESMTP id 4E0AED1D489 for ; Fri, 13 Feb 2004 16:29:28 -0400 (AST) Received: (from andrew@localhost) by pillette.com (8.11.6/8.11.6) id i1DKTWp01272; Fri, 13 Feb 2004 12:29:32 -0800 Date: Fri, 13 Feb 2004 12:29:32 -0800 From: andrew@pillette.com Message-Id: <200402132029.i1DKTWp01272@pillette.com> Subject: Doc bug (?) in rules vs triggers To: pgsql-docs@postgresql.org Cc: X-Originating-IP: 192.168.1.203 X-Mailer: Webmin 0.940 MIME-Version: 1.0 X-Virus-Scanned: by amavisd-new at postgresql.org Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Archive-Number: 200402/15 X-Sequence-Number: 2270 Chapter 13 of the documentation on Rules versus Triggers says in part "On the other hand a trigger that is fired on INSERT on a view can do the same as a rule, put the data somewhere else and suppress the insert in the view." However, it does not appear to be possible to set a trigger on a view, so this means something else. (I'd like to set a trigger on a view, because the replacement INSERT I wish to make is easier to write in PLPGSQL than plain SQL.)