Re: Trigger

From: Sybrand Bakker <gooiditweg_at_sybrandb.nospam.demon.nl>
Date: Fri, 03 Oct 2003 19:24:22 +0200
Message-ID: <84crnv036n6sl6ugi9ujrlnr004r974o81@4ax.com>

On 3 Oct 2003 01:37:09 -0700, grudnevkv_at_yandex.ru (Konstantin Grudnev) wrote:

>Dear, All !
>
>I have two databases linked to each other and I have two UPDATE
>triggers in both databases. Here what I have
>The first database called FIRSTDB and the second database called
>SECONDDB
>in FIRSTDB I have table FIRSTTABLE and SECONDTABLE in SECONDDB.
>FIRSTTABLE has UPDATE trigger which updates SECONDTABLE, and
>SECONDTABLE also has UPDATE trigger which updates FIRSTTABLE. I guess
>it's not right solution, because this UPDATE triggers recusively call
>each other, which is not good.
>I want next scenario:
>update table FIRSTTABLE -> UPDATE trigger in FIRSTTABLE called ->
>SECONDTABLE updated.
>In this chain shouldn't be a call of the SECONDTABLE's UPDATE trigger.
>
>How can I achieve this ?

I guess simply disabling or dropping the trigger on secondtable would be sufficient. If you don't think so, I am afraid you'll need to go into more detail

--
Sybrand Bakker, Senior Oracle DBA

Received on Fri Oct 03 2003 - 12:24:22 CDT