Re: Checking for uncommited transactions

A transaction starts when a uses STARTS changing something and ENDS when the user COMMITS or ROLLS BACK.
In case of error, the FAILING statement is rolled back automatically, if you want to rollback (or commit) any other uncommitted data resulting from previous statements, then you have to explicitly roll back (or commit). And, of course, I am talking of pure INSERTS, DELETES and UPDATES, not TRUNCATES or whatever else.

I know very well all this stuff.

The original question has very little to do with this. Moreover I never mentioned Oracle Forms, I never used it in my life, I am talking of a more general concept of form like a form created in VB.

Flavio

"Sybrand Bakker" <gooiditweg_at_sybrandb.demon.nl> wrote in message news:0t5f6vsi5pok5etpbo943qrusivjd6f9bj_at_4ax.com...
> On Thu, 06 Mar 2003 17:36:22 GMT, "FC" <flavio_at_tin.it> wrote:
>
> >What's wrong with this scenario?
> >
>
>
> Read up transactions in the Oracle Concepts manual, starting at the
> very first line.
>
> If an user 'exits from the form' he/she either needs to COMMIT or to
> ROLLBACK, because he/she started a transaction. A transaction starts
> whenever the user changes ANYTHING.
> Users also DON'T make LOCAL CHANGES in a form, they are ALWAYS
> changing the database DIRECTLY.
>
> You aren't OCP, by any chance?
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Fri Mar 07 2003 - 04:02:51 CST