Transactional haywire...

Does anyone know a way to implement following scenario in a single transaction:

From a VB application we connect to Oracle over OleDB to execute a couple of stored procs in following way:

• Application goes to the DB as user uA executing procedure pA
• Application goes to the DB as user uB executing procedure pB
• Commit or rollback (all or nothing)

pA does a couple of things in the DB that allow pB later on to delete data without being faced with foreing key constraints, so it's not an option to have pA not commit because pB needs to be able to see the results of pA while being logged to Oracle under another user account.

There are several reasons (on which I won't elaborate here) why we can't use a single user to do the work.

Any comments appreciated.

Peter Received on Wed Feb 04 2004 - 12:40:51 CET