Author palaviv
Recipients berker.peksag, fschulze, ghaering, jaraco, ned.deily, palaviv, r.david.murray, serhiy.storchaka, socketpair, xiang.zhang
Date 2016-11-25.14:35:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480084554.6.0.938096100893.issue28518@psf.upfronthosting.co.za>
In-reply-to
Content
There are already a few test's that start a transaction explicitly:

In dbapi.SqliteOnConflictTests CheckOnConflictRollbackWithExplicitTransaction, CheckOnConflictAbortRaisesWithExplicitTransactions which set ``isolation_level = None``.

On the other hand in transaction.TransactionalDDL.CheckTransactionalDDL the test do not set the isolation_level to None but start a transaction explicitly. The test pass because sqlite3_stmt_readonly return true for "begin" and "begin deferred".

I think that if we say that in order to start a transaction implicitly the isolation_level needs to be None CheckTransactionalDDL should be changed.
History
Date User Action Args
2016-11-25 14:35:54palavivsetrecipients: + palaviv, ghaering, jaraco, ned.deily, r.david.murray, socketpair, berker.peksag, serhiy.storchaka, xiang.zhang, fschulze
2016-11-25 14:35:54palavivsetmessageid: <1480084554.6.0.938096100893.issue28518@psf.upfronthosting.co.za>
2016-11-25 14:35:54palavivlinkissue28518 messages
2016-11-25 14:35:54palavivcreate