Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Checking for uncommited transactions
Hello Oraclers,
I was asking myself what are the possible drawbacks of the following
approach:
I've some client front-ends modifying data by means of stored procedures and
they are allowed to change several values on different tables before
committing or rolling back.
Instead of maintaining a flag indicating whether something has changed on
the client, I was wondering about the possibility of evaluating a function
or alike that checks for any pending locks (via V$LOCKED_OBJECT presumably)
against its session id.
Any thoughts about this?
Bye,
Flavio
Received on Wed Mar 05 2003 - 14:14:52 CST
![]() |
![]() |