Re: AutoCommit - Oracle.
From: Eric (Eric_at_nospam.com)
Date: 02/15/05
- Next message: Craig Wagner: "Re: Passing in SqlConnection by ref"
- Previous message: Jim Heavey: "Access Security Issue"
- In reply to: Jim Heavey: "Re: AutoCommit - Oracle."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 14 Feb 2005 23:40:51 -0500
Jim Heavey wrote:
> I guess I always thought the Oracle stored procedures should be self
> contained for anyone who wanted to use them...so if I was using Toad on SQL+
> and invoked the stored procedures, the user would not have to worry about
> having to have to commit the transaction.
This is incorrect. Oracle never autocommits. TOAD has a configuation
setting to indicate if you want it to commit when you exit, but there is
no autocommit in TOAD until you exit.
I never knew Sqlplus to autocommit, but I haven't used it in a few years
so I can't comment on it.
SQL Server has always had a database option for this because it came
from Sybase.
Unlike SQL Server, Oracle is always in a transaction...COMMIT or
ROLLBACK ends the current tranaction and starts the next one.
When it comes to SPs, you should have 2 types of SPs: those with an
external interface can be used to control transactions, but those that
are only internal should not be used to control transactions.
If you use ADO.NET you have to pay close attention to who controls each
transaction.
It's critically important if you have linked DBs and distributed
transactions (updates accross DB boundaries).
Eric
- Next message: Craig Wagner: "Re: Passing in SqlConnection by ref"
- Previous message: Jim Heavey: "Access Security Issue"
- In reply to: Jim Heavey: "Re: AutoCommit - Oracle."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
