| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Insert Trigger problem
There is no order to rows in a relational table. Each row is independent of
the others (of course that doesn't mean that some vendors don't ignore
this). Can you try adding a flag to your fields to accomplish what you need?
Henry
-----Original Message-----
From: Helmut Daiminger [mailto:hdaiminger_at_vivonet.com]
Sent: Friday, December 15, 2000 1:40 PM
To: Sawyer Joey; Oracle List (Telelist); Oracle DBA List (Lazy DBA);
Frach Karsten; Eftimescu Nico
Subject: Insert Trigger problem
Hi!
I am having an interesting problem here:
A user is inserting a record into table A. This table has an after insert trigger associated with it that inserts three rows in table RESULT. Shortly after that, the user inserts a record into table B. This table has an after insert trigger associated with it that inserts 500 rows in table RESULT. Now the user goes back to table A and inserts another record into table A, which causes the trigger to insert another three recors in the table RESULTS. Then the user inserts into table B again... And so on and so forth.
The question is: does the trigger on table A (when it is called the second time) wait for the 500 records from the table B trigger to be inserted or does it fire right away when the user inserts another record?
The deal is that we need the records in the RESULT table to be in a specific order. In other words: the trigger on table A would have to 'wait' for the trigger on table B (that is inserting far more records) to finish before it is executing again.
Is there any way to do that?
This is 8.1.6 on Win2k.
Thanks,
Helmut
PS: Does anybody have an idea how SQL Server 7 handles that problem? Because we would have to do the same thing on SQL Server 7 as well...
 |
 |