Re: uncomitted data gets committed when application dies

From: Volker Hetzer <volker.hetzer_at_ieee.org>
Date: Thu, 9 Dec 2004 17:02:14 +0100
Message-ID: <cp9su5$nv3$1@nntp.fujitsu-siemens.com>

"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> schrieb im Newsbeitrag news:41b7fcb8$0$19157$cc9e4d1f_at_news-text.dial.pipex.com...
> "Sybrand Bakker" <sybrandb_at_hccnet.nl> wrote in message
> news:1rper092kfnnt5d1b7rin9q054u0n9s5th_at_4ax.com...
> > On 8 Dec 2004 09:41:49 -0800, yong321_at_yahoo.com wrote:
> >
> >>Does this problem only happen to your OraTcl session? I can't imagine
> >>it happens to a sqlplus session.
> >
> > It definitely does. Both exit and quit perform an implicit commit, as
> > does disconnect. And of course all of this is documented...
>
> See Rauf's example, we are not talking about normal termination but abnormal
> termination of the client. If apps that crashed left data that they'd
> half-processed committed we'd be in a lot worse state wrt data quality than
> we already are. I'd forgotten about SET AUTOCOMMIT in sqlplus, but that
> would explain it as well. There is a brief discussion of how to set
> autocommit in oratcl at http://www.orafaq.com/faqtcl.htm
It is set off. definitely. However, I'm going to do an oci testcase.

Lots of Greetings!
Volker Received on Thu Dec 09 2004 - 10:02:14 CST