Hi Michael,
I only noticed the activity on this thread today.
On Sat, 2010-08-14 at 11:07 -0400, Michael Bayer wrote:
reproduce the problem and it suggests the problem stems from some
behaviour of transactions or of the engine.base.Connection class. I
don't quite know what to make of it
On Nov 2, 2010, at 5:15 PM, Torsten Landschoff wrote:
In addition, isolation_level=None with pysqlite disables the DBAPIs entire
transactional system. SQLAlchemy relies upon this system to handle proper
transactional behavior. Per their documentation, some statements will fail
if
On Aug 13, 2010, at 10:22 PM, Peter Hansen wrote:
On Jun 24, 1:23 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On Jun 24, 2010, at 12:35 PM, Torsten Landschoff wrote:
That's what I thought but it does not cure my problem.
e.raw_connect().isolation_levelis in fact None, but the rollback
On Aug 14, 2010, at 12:04 PM, Peter Hansen wrote:
On Aug 14, 11:07 am, Michael Bayer mike...@zzzcomputing.com wrote:
In addition, isolation_level=None with pysqlite disables the DBAPIs
entire transactional system. SQLAlchemy relies upon this system to
handle proper transactional behavior.
