PEP 249 requires autocommit to be initially off

waliwali / ibm-db

Automatically exported from code.google.com/p/ibm-db

0 stars 0 forks source link

PEP 249 requires autocommit to be initially off #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Looking at the source of the 0.2.7 release, the connect method passes in
SQL_AUTOCOMMIT_ON if no autocommit option is specified in the connection
parameters. This is inconsistent with the requirements of PEP 249 (refer to
the documentation of the commit() method in the PEP).

Original issue reported on code.google.com by malc...@pointy-stick.com on 21 Mar 2008 at 7:54

GoogleCodeExporter commented 9 years ago

I should have pointed out, in case it wasn't clear, this is in ibm_db_dbi.py.

Original comment by malc...@pointy-stick.com on 21 Mar 2008 at 8:12

GoogleCodeExporter commented 9 years ago

Agreed.
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."

Original comment by apiti...@ca.ibm.com on 24 Mar 2008 at 1:36

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Internal defect #156919

Original comment by apiti...@ca.ibm.com on 24 Mar 2008 at 6:16

Changed state: Started

GoogleCodeExporter commented 9 years ago

Fixed in ibm_db-0.2.8

Original comment by apiti...@ca.ibm.com on 28 Mar 2008 at 10:11

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Original comment by abhigyan...@in.ibm.com on 28 Apr 2008 at 2:32

Changed state: Verified

GoogleCodeExporter commented 9 years ago

Please see issue 103. When conn_options is None, autocommit is set to on when 
it should be off.

Original comment by sok...@gmail.com on 5 Apr 2012 at 10:52