Issue 8: pyodbc seems to always use autocommit with Oracle
Status:  NoFix
Owner: ----
Closed:  Dec 2008
Reported by ch.zwerschke@gmail.com, Dec 3, 2008
Is this a known problem?

I'm using the Oracle 10g client on WinXP and data is written to the
database even though I haven't set autocommit (or set it explicitely to
false) and never call the commit() method.
Dec 3, 2008
Project Member #1 mkleehammer
It's not a known issue.  It is possible that the call to set autocommit is failing
and pyodbc ate the error.

Can you turn on ODBC tracing and try a very simple test?  Maybe just connect, insert
one record, then exit without committing?
Status: Investigating
Dec 3, 2008
#2 ch.zwerschke@gmail.com
Sorry, false alarm. The problem was an alter trigger command in my transaction. I
forgot that in Oracle, as any DDL statement, this will automatically cause a commit
on the current transaction. After moving the DDL outside the transaction, everything
worked as expected. Thanks for the quick response.
Dec 3, 2008
Project Member #3 mkleehammer
(No comment was entered for this change.)
Status: Invalid
Nov 21, 2010
Project Member #4 mkleehammer
(No comment was entered for this change.)
Status: NoFix