Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: uncomitted data gets committed when application dies

Re: uncomitted data gets committed when application dies

From: Niall Litchfield <niall.litchfield_at_dial.pipex.com>
Date: Wed, 8 Dec 2004 18:13:22 -0000
Message-ID: <41b74438$0$19160$cc9e4d1f@news-text.dial.pipex.com>


"Volker Hetzer" <volker.hetzer_at_ieee.org> wrote in message news:cp7b44$g0a$1_at_nntp.fujitsu-siemens.com...
> Hi!
> I've got a problem with a library I use for accessing oracle.
> Basically, I use Oratcl ans Tcl/Tk and I take a lot of care not to
> commit any data if everything is not in order. But, if the app gets
> killed for some reason, the *uncomitted* data appears visible in
> the database!
> I just contacted the guy who wrote the Oratcl extension and
> his answer was:
>
> "This seems to be standard behavior with oracle client libraries.
> I have had this happen in multiple oracle versions and with SQL*Plus."

I'd like to see evidence of that, it certainly *isn't* standard SQL*Plus behaviour. I know that by default JDBC and ODBC drivers tend to commit after each statement - maybe this is what he meant?

-- 
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com 
Received on Wed Dec 08 2004 - 12:13:22 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US