From: Rajesh Kumar Mallah. <mallah@trade-india.com>
To: wit <microx@hotpop.com>
To: pgsql-sql@postgresql.org
Subject: Re: check source of trigger
Date: Thu, 26 Sep 2002 23:43:16 +0530
Message-ID: <200209262343.16976.mallah@trade-india.com> (raw)
In-Reply-To: <amem61$1j4o$1@news.hub.org>
References: <amem61$1j4o$1@news.hub.org>
Hi,
In case you doing all this to replicate tables
conside contrib/dbmirror it does it fairly elegantly.
regds
mallah.
On Friday 20 September 2002 13:55, wit wrote:
> Hello,
>
> I have a question about trigger. I have tables with the following
> structure:
>
> create table A (
> e_codeA char(5) default '' not null,
> n_codeA varchar(20) default '' not null,
> constraint A_pkey primary key ( e_codeA )
> );
>
> create table B (
> e_codeB char(5) default '' not null,
> e_codeA char(5) default '' not null
> constraint e_codeA_ref references A( e_codeA )
> on delete cascade on update cascade,
> n_codeB varchar(20) default '' not null,
> constraint B_pkey primary key ( e_tranB, e_codeA )
> );
>
> I have trigger and procedure on table B to capture any change and insert
> into table logB:
> create trigger trigger_b before insert or update or delete on B for
> each row execute procedure log_change();
>
> When I update e_codeA in table A, the constrain trigger will update e_codeA
> in B. My trigger, trigger_b, also was trigged and procedure will record
> change into table logB too.
> How to write a code in my db procedure to check whether the procedure was
> called by normal SQL or was called by cascade trigger.
>
> Regards,
> wit
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)
Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mallah@trade-india.com, microx@hotpop.com
Subject: Re: check source of trigger
In-Reply-To: <200209262343.16976.mallah@trade-india.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox