pymssql defaults to auto-commit=True

[GoogleCodeExporter]

new connections opened with pymssql should probably execute "SET 
IMPLICIT_TRANSACTIONS ON;" before returning to the user.  this is to maintain 
compliance with the DB-API spec.

from http://www.python.org/dev/peps/pep-0249/:

"Note that if the database supports an auto-commit feature, this must be 
initially off.  An interface method may be provided to turn it back on."

>>> pymssql.__version__
'1.0.2'

Original issue reported on code.google.com by pub...@kered.org on 11 Aug 2010 at 9:53

[GoogleCodeExporter]

This is fixed in trunk now, autocommit already defaults to False in trunk but 
now also calls SET IMPLICIT_TRANSACTIONS ON, thanks for the suggestion.

Original comment by dam...@gmail.com on 4 Jan 2011 at 7:53

• Changed state: Fixed

[GoogleCodeExporter]

I am going to revert this actually in hindsight. I think you may have 
misinterpreted how IMPLICIT_TRANSACTIONS work, it opens a transaction and then 
leaves it open, which is quite odd behaviour and just caused a few hours 
debugging.

pymssql opens a transaction when it initially connects so there is no 
autocommit, at least in 1.9.909.

Original comment by dam...@gmail.com on 24 Feb 2011 at 3:42

• Changed state: WontFix

[GoogleCodeExporter]

> in hindsight. I think you may have misinterpreted how IMPLICIT_TRANSACTIONS 
work

I agree.  Still the issue remains in 1.0.2 that pymssql autocommits after every 
execute.  Glad to hear it's fixed in head tho.  :)

Original comment by pub...@kered.org on 24 Feb 2011 at 4:58