Received: from jupiter.hub.org (jupiter.hub.org [64.49.215.5]) by postgresql.org (Postfix) with ESMTP id DE1E24766A0 for ; Mon, 11 Mar 2002 13:35:40 -0500 (EST) Received: (from news@localhost) by jupiter.hub.org (8.11.6/8.11.6) id g2BIIZQ39585 for pgsql-sql@postgresql.org; Mon, 11 Mar 2002 12:18:35 -0600 (CST) (envelope-from news) From: Mike Finn X-Newsgroups: comp.databases.postgresql.sql Subject: Calling a trigger from a trigger Date: Mon, 11 Mar 2002 11:19:00 -0700 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 21 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: news@hub.org User-Agent: KNode/0.6.1 To: pgsql-sql@postgresql.org X-Archive-Number: 200203/160 X-Sequence-Number: 7040 I have a number of tables that have a group of fields in common. I want to process theses fields in a before trigger (before insert or update), but each of the tables have before triggers for processing of other non-common data fields. It seems that from a pl/pgsql trigger I cannot call another trigger (the one that would be common to all) and if I just attach the common trigger as a second trigger to each table then (according to the docs) there is no guarantee of the execution order (which I need ... each table requires the common stuff to be processed before the non-common stuff). Is there a way to achieve this requirement without duplicating the code from the common-part in each of table triggers? Thanks, in advance, for any thoughts Mike. ========================================= Mike Finn mike.finn@tacticalExecutive.com