Firing Sequence in D2K

On Nov 29, 1: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

Have you tried googling the following phrase:
firing sequence of oracle forms developer 2000

jg
--
@home.com is bogus.
http://tech.fortune.cnn.com/2010/11/...-oracle-hates/

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.

On Nov 29, 12:52*pm, joel garry wrote:
> On Nov 29, 1: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
>
> Have you tried googling the following phrase:
> firing sequence of oracle forms developer 2000
>
> jg
> --
> @home.com is bogus.http://tech.fortune.cnn.com/2010/11/...-oracle-hates/

Joel's suggested tested well via Bing. We still run Forms 6i so I may
have to read some of those posts.

HTH -- Mark D Powell --

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.

jg
--
@home.com is bogus.
What do you call it when you do the same thing over and over expecting
different results? QA testing.