× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That seems perfectly normal to me. In fact I would be surprised if the
database software started separate threads for each of the triggers.
That would be just asking for trouble.

PC2

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Yan.Zhang@xxxxxxxxxx
Sent: August 25, 2010 13:58
To: Java Programming on and around the iSeries / AS400
Subject: SQL trigger question

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.


thanks,
YanZ
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 by midrange.com 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.