Re: Firing Sequence in D2K

From: joel garry <>
Date: Wed, 1 Dec 2010 10:23:39 -0800 (PST)
Message-ID: <>

On Nov 29, 2:06 pm, Steve Howard <> wrote:
> On Nov 29, 4:01 am, Sonal <> wrote:
> > Q= What is the firing sequence in oracle forms of the below triggers:
> > - On-Insert
> > - On-Delete
> > - On-Update
> > when in forms, we insert, delete and update the transactions
> > simultaneously of the same block.
> > regards
> > Sonu
> In addition to what Joel suggested, you can always turn on trace for
> the session and review it to absolutely verify the order.

Empirical tests like that are why people conclude things like you don't need an order by to get stuff out of a database in the same order you put it in. You always need to know the limits of your instrumentation. That said, tracing is maybe the best you can do, when combined with edge cases. Which pushes the question to defining the edge cases.

I can understand tkyte's aversion to triggers.


-- is bogus.
What do you call it when you do the same thing over and over expecting
different results?  QA testing.
Received on Wed Dec 01 2010 - 12:23:39 CST

Original text of this message