There is a "FOR EACH STATEMENT" or "FOR EACH ROW" option in the create
trigger. The first is the default. I think it will cause the triggers to
fire once if there are several rows inserted in the same statement.

Alan Campin wrote:
Any commit control in the mix.

The triggers will fire sequentially I think based on the order the triggers
where added to the table.

On Wed, Aug 25, 2010 at 2:58 PM, <Yan.Zhang@xxxxxxxxxx> wrote:

I have 3 "after update" triggers on Table0: T1, T2, and T3. All these 3
triggers are built on Table0.
T1 inserts some records into Table1;
T2 inserts some records into Table2;
T3 inserts some records into Table3.

So, after Table0 is updated, I think T1,T2.and T3 would be launched at the
same time.
But why in my experiments it shows the "insert into...." for 3 tables are
executed sequentially? i.e. A bunch of records are inserted into Table1,
then a bunch of records are inserted into Table2, then a bunch of
records are inserted into Table3.

This is the Java Programming on and around the IBM i (JAVA400-L) mailing
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.