Regarding Trigger costraint

bootstrap wrote:There is a table say T1 where in data is inserted in T1 through database link from other database. A Trigger on T1 table inserts data in another table T2.Is it possible to have another insert trigger on table T2 which inserts data in another table T3.Is there any constraint in defining trigger on table T2 ?

Technically, no.  But this is very suggestive of a poorly thought out design.  What is the relationship of the three tables, and what business purpose is achieved by these cascading triggers?

bootstrap, we have a process running on a factory server that inserts a row into a materials server table with an insert row trigger which then inserts into another table with an insert row trigger until six such triggers fire.  The last trigger inserts a row back to the source database.  Control is returned to the caller at which point the program reads the return row.  This process has worked without issue since version 7.x.

- -

Basic rule - trigger code should only act upon another table and when target tables have triggers the logic should never refer back to a prior tables in the stream.  Don't use additional triggers where the first trigger or calling process could just perform multiple DML operations itself.

- -

HTH -- Mark D Powell --