If he is trying to do some sort of auditing thing where he wants the insert
and update to occur even if the rest is rolled back he could use autonomous
transactions in 8.1.7
Jim
"Nuno Souto" <nsouto_at_optushome.com.au.nospam> wrote in message
news:3b6426ef.11560892_at_news...
> On Sun, 29 Jul 2001 14:53:19 GMT, e9926043_at_student.tuwien.ac.at
> (Sebastian Scholz) wrote:
>
> >I'm using some PL/SQL Code inside a Trigger. Two Statements (INSERT
> >AND UPDATE) MUST execute at a transaction basis. Unfortunately,
> >commits and rollbacks aren't allowed.
> >
> >What exactly happens if after the first INSERT Statement the machine
> >or ORacle goes down?
>
> It gets rolled back.
>
> >If these Statements don't execute within a
> >Transaciton, how do I accomplish that?
> >
>
> You commit after executing the statement against the table that causes
> the trigger to fire.
>
>
> Cheers
> Nuno Souto
> nsouto_at_optushome.com.au.nospam
Received on Sun Jul 29 2001 - 10:40:33 CDT
