RE: functions/procedures and commits

2003-01-06 Thread Sinardy Xing
Hi John Dunn, My answer is never commit, Oracle will rollback. Are you consider auto commit an implicitly commitment? Sinardy -Original Message- Sent: 02 January 2003 22:14 To: Multiple recipients of list ORACLE-L Under what circumstances is a COMMIT done implicitly? If I call

Re: functions/procedures and commits

2003-01-02 Thread Rachel Carmichael
if I recall correctly, implicit commits are done a) on a clean exit from sqlplus b) on a clean exit from a stored program c) if you do a DDL statement after the DML statement but this is from memory and without checking manuals. --- John Dunn [EMAIL PROTECTED] wrote: Under what

RE: functions/procedures and commits

2003-01-02 Thread Jamadagni, Rajendra
Title: RE: functions/procedures and commits No ... an implicit commit is performed 1. If you perform any DDL statement 2. If SQLPLUS you exit without issuing an explicit ROLLBACK. Otherwise, your transaction will remain open awaiting for an explicit commit or rollback. Raj

RE: functions/procedures and commits

2003-01-02 Thread Mercadante, Thomas F
John, there is no such thing as an implicit commit within Oracle. the only implicit commit that I know of is during a sqlplus session when you exit the program. even this is settable by a sqlplus option. distributed transactions that are controlled by a transaction coordinator (like MS DTC)

RE: functions/procedures and commits

2003-01-02 Thread John Weatherman
9:29 AMTo: Multiple recipients of list ORACLE-LSubject: RE: functions/procedures and commits No ... an implicit commit is performed 1. If you perform any DDL statement 2. If SQLPLUS you exit without issuing an explicit ROLLBACK. Otherwise, your transaction will remain open

RE: functions/procedures and commits

2003-01-02 Thread John Weatherman
Tom, Oracle issues an implicit commit any time DDL is performed or when a quit/exit is issued (Complete Ref p285) or after a set number of commands by using a set autocommit # (Complete Ref 283). With the latter is arguably not truly an implicit commit, as you do set it, DDL most certainly is.

RE: functions/procedures and commits

2003-01-02 Thread Fink, Dan
Tom, I must respectfully disagree. Explicit = a COMMIT or ROLLBACK is explicitly issued by the user/program. Implicit = a COMMIT or ROLLBACK is performed as the result of an action and not issued by the user/program. The SQL*Plus options AUTOCOMMIT and COPYCOMMIT do not control

RE: functions/procedures and commits

2003-01-02 Thread Koivu, Lisa
Coconut Creek Parkway Ft. Lauderdale, FL, USA 33063 -Original Message-From: John Weatherman [mailto:[EMAIL PROTECTED]]Sent: Thursday, January 02, 2003 10:41 AMTo: Multiple recipients of list ORACLE-LSubject: RE: functions/procedures and commits Or if you set autocommit

RE: functions/procedures and commits

2003-01-02 Thread Mercadante, Thomas F
Dan, I agree with you and I think I said the same thing - though not as lengthy! :) As you said, the Sql*Plus AutoCommit option controls issuing a commit upon exiting the program. As I said in a prior mail, I did not mention DDL forcing an implicit commit as the question pertained to INSERT

RE: functions/procedures and commits

2003-01-02 Thread Fink, Dan
AUTOCOMMIT controls COMMITs after execution of individual DML statements, not upon EXITing SQL*Plus. The point I want to make is that IMPLICIT COMMITs ROLLBACKs do occur. I have encountered the following scenario more than once... 'Oracle is not saving changes' is the complaint from the users.