Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f54JWHE88652; Mon, 4 Jun 2001 15:32:17 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.10.1/8.10.1) id f54JW8003774; Mon, 4 Jun 2001 15:32:08 -0400 (EDT) From: Bruce Momjian Message-Id: <200106041932.f54JW8003774@candle.pha.pa.us> Subject: Re: Update needed for documentation In-Reply-To: <3AFB97B9.4B928AF8@postgresql.org> "from Justin Clift at May 11, 2001 05:41:45 pm" To: Justin Clift Date: Mon, 4 Jun 2001 15:32:08 -0400 (EDT) CC: pgsql-docs@postgresql.org X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200106/6 X-Sequence-Number: 801 > Hi all, > > Spotted the following line in the 7.1 Interactive docs, not sure if it's > been updated : > > "As of the current release (v7.0), STATEMENT triggers are not > implemented." > > It's in the PostgreSQL Doc page which explains "CREATE TRIGGER". I see in command/trigger.c: if (stmt->row) TRIGGER_SETT_ROW(tgtype); else elog(ERROR, "CreateTrigger: STATEMENT triggers are unimplemented, yet"); We have per-row triggers but not per-statement triggers. Seems we use RULEs for those. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026