FreeTDS Development Group

["Michael Horowitz" <michael.horowitz AT storagenetworks.com>]

Well, you have to read more carefully.  Oracle won't commit if a
connection dies or is killed or terminates abnormally.  It is only if the
client explicitly disconnects.  I am not exactly sure if that only entails
calling "close" on the underlying socket, or if there is a formal logout
protocol, but either way, if disconnect() is explicitly called from DBI or
a similar thing from any other DB library, it says it will commit the
transaction.

Personally, I don't like the idea of that either.  It seems to me that a
explicit commit should always be required, but that is the way Oracle
chose to do it I guess.

--Mike

> I don't believe Oracle commits the transaction.  I've killed many users with
> open transactions and they do not get commited.  I suppose I could create a
> test app and verify it.
> 
> -----Original Message-----
> From: Michael Peppler [mailto:mpeppler AT peppler.org]
> Sent: Thursday, January 03, 2002 12:05 PM
> To: TDS Development Group
> Subject: [freetds] Re: Transaction problems...
> 
> 
> Michael Horowitz writes:
>  > I don't know if this is the same issue, but I remember reading about
>  > issues with disconnects and commit/rollbacks with the Perl DBI module.
> It
>  > said, "The transaction effect of explicitly disconnecting from a database
>  > while AutoCommit is disabled is, sadly, undefined.
> 
> Sybase will rollback any transactions that aren't committed when the
> connection is dropped. I find Oracle's behaviour inexplicable. I
> suspect that MS-SQL has the same behaviour.
> 
> Michael
> -- 
> Michael Peppler - Data Migrations Inc. - http://www.mbay.net/~mpeppler
> mpeppler AT peppler.org - mpeppler AT mbay.net
> International Sybase User Group - http://www.isug.com
> 
> ---
> You are currently subscribed to freetds as: [jfisher AT emery-waterhouse.com]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')