uncomitted data gets committed when application dies

From: Volker Hetzer <volker.hetzer_at_ieee.org>
Date: Wed, 8 Dec 2004 17:45:57 +0100
Message-ID: <cp7b44$g0a$1@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."

Is there any way I can configure the session or the database to rollback any uncomitted changes when the database detects a dead session?

Lots of Greetings!
Volker Received on Wed Dec 08 2004 - 10:45:57 CST