Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 42E3C476302 for ; Sat, 3 Aug 2002 14:34:58 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id C12E04763E6 for ; Sat, 3 Aug 2002 14:34:56 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g73IYiVk004171; Sat, 3 Aug 2002 14:34:45 -0400 (EDT) To: Marc SCHAEFER Cc: pgsql-sql@postgresql.org Subject: Re: Triggers for inserting on VIEWS In-reply-to: References: Comments: In-reply-to Marc SCHAEFER message dated "Sat, 03 Aug 2002 20:04:25 +0200" Date: Sat, 03 Aug 2002 14:34:44 -0400 Message-ID: <4170.1028399684@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/60 X-Sequence-Number: 8906 Marc SCHAEFER writes: > at least with PostgreSQL 7.1 it was possible to create a trigger on a > view. Use a rule instead. 7.2 will reject an attempt to insert into a view without a replacement rule, so a trigger would do you no good anyhow. (I thought that behavior went back further than 7.2, actually.) regards, tom lane