On Wed, 8 Dec 2004, niall.litchfield_at_dial.pipex.com wrote:
> "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?
The default for jdbc is to autocommit. You have to set it on the
jdbc connection object.
--
Galen Boyer
Received on Wed Dec 08 2004 - 13:30:24 CST
