[pysqlite] transaction and DML statement

Hi there,

some time ago I posted a ticket [1] in regards to the fact that pysqlite
was emitting as COMMIT before a DML statement was executed. This ticket
has been rejected for backward compatibility reason. Fine, but I still
can't find a way to avoid this, while the documentation states [2]:

  "By default, pysqlite opens transactions implicitly before a DML
   statement (INSERT/UPDATE/DELETE/REPLACE), and commits transactions
   implicitly before a non-DML, non-DQL statement (i. e. anything other
   than SELECT/INSERT/UPDATE/DELETE/REPLACE)."

"By default" makes me think that I can do something to avoid this
behaviour, but I can't find what... The connexion's isolation_level
attribute mentionned seems to only control the type of BEGIN statement
emited. Did I miss something ?

If not, that would be very nice to provide a way to acheive this in a
backward compatible way, such as a special connection attribute.

Thanks in advance

[1] http://oss.itsystementwicklung.de/trac/pysqlite/ticket/219
[2] http://www.initd.org/pub/software/pysqlite/doc/usage-guide.html#controlling-transactions

PS: please include my address in reply, I'm not subscribed to this list.
-- 
Sylvain Thénault                               LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian:  http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
Python et calcul scientifique:           http://www.logilab.fr/science

_______________________________________________
list-pysqlite mailing list
[email protected]
http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite