Re: Nested Transaction Level

Hello,

nospam wrote:
>
> Thats' ok, thanks.
>
> But I can call the same function at the top level or in a nested function...

If you know a set of functions that could call your function, you can play with scripts from Thomas Kyte 'Who Called Me' and determinated if you need to do commit or not.
http://govt.us.oracle.com/~tkyte/who_called_me/index.html

Hth,

Erika

>
> So I need a dynamic way to choose when to commit (if the function is called
> at the top level) or not (if the function is called by another function
> which will do the commit).
>
> I'm looking for a system view o something similar which can tell me if I am
> in a nested transaction or in a nested function.
>
> Thanks a lot.
>
> _-^-_nto
>
> "Frank" <franjoe_at_frisurf.no> ha scritto nel messaggio
> news:8ZQp6.10293$t21.277051_at_news3.oke.nextra.no...
> > Hi!
> >
> > When you perform a commit; or rollback; all outstanding transaction in you
> > current session
> > are handled, regardless of which procedure/function-stack level you are
 in.
> >
> > So; yes the commit in SP_BBB will commit everyting since the last
> > commit/rollback (including rollback to savepoints) in the session
> > (also if that was "outside" SP_AAA"), and your savepoint will be lost.
> > If you wish these to procedures to have a transaction-context each,
 perhaps
> > you should look at
> > Autonomus Transactions in Oracle 8(?)/8i.
> > Otherwise, you can remove the commit in SP_BBB because it will be
 commit'ed
> > in SP_AAA anyway.
> >
> >
> > Frank
> >
> >
Received on Fri Mar 09 2001 - 04:49:08 CST