Re: Transactional haywire...
Date: 4 Feb 2004 06:29:58 -0800
Message-ID: <c0e3f26e.0402040629.7abd32c2_at_posting.google.com>
peter1_at_mail.be (Peter) wrote in message news:<7912d63f.0402040340.75f13943_at_posting.google.com>...
> 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
Of course the answer is "you can't". But you knew that already, didn't you? You really should elaborate on why you have to do it that way. It might give an insight into the solution. Received on Wed Feb 04 2004 - 15:29:58 CET