Re: Checking for uncommited transactions

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: 12 Mar 2003 00:43:50 -0800
Message-ID: <a20d28ee.0303120043.2c186dde@posting.google.com>

"Immo Landwerth" <mail_ignored_at_web.de> wrote in message news:<b4m7rf$21q2g7$1_at_ID-169341.news.dfncis.de>...
> Galen Boyer wrote:
>

>> What I meant is that transactions should not be commited/rollbacked
> from the client app.

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG

>
> Look at our scenario. Let's assume the client will crash/hang after the
> insert or the user leaves his workstation. In this case _no_ user is
> able to delete a record in USERS.
>

PMON will roll back the transaction!!!!!!!!!!!!!!

> To avoid this problem (in most cases) all transactions should be
> encaspulated in pl/sql code. After the excecution no transactions
> should be open anymore.
>

Question: where does the pl/sql code run? Answer: in the USER's!!!!! session.
So what does this change????

ZERO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

> In simple words: Don't give the end-user the control over transactions.

That is the most stupid assertion I ever saw in this group. It is also NOT possible, NEVER!!!!!!

Regards

Sybrand Bakker
Senior Oracle DBA Received on Wed Mar 12 2003 - 02:43:50 CST