Author dholth
Recipients asvetlov, dholth, ghaering, r.david.murray, scott.urban
Date 2011-02-18.21:17:19
SpamBayes Score 2.85799e-11
Marked as misclassified No
Message-id <1298063843.2.0.816933382266.issue10740@psf.upfronthosting.co.za>
In-reply-to
Content
I want transactional DDL too. I was tremendously surprised that I could not duplicate the way sqlite3 behaves on the command line from witin pysqlite.

Instead of this patch, I would rather be able to instruct pysqlite to always begin a transaction for any kind of statement (I hear this is a requirement for DB-API compliance) and never perform an implicit commit for any reason. For example, someone on the google code project had a complaint that 'SAVEPOINT' (create a subtransaction) automatically commits because pysqlite doesn't know about it.

I tried to trick pysqlite into doing what I wanted by prepending /* update */ to every CREATE TABLE statement but it didn't seem to quite work. Instead, I would prefer a pysqlite that does not strcmp(statement) at all.
History
Date User Action Args
2011-02-18 21:17:23dholthsetrecipients: + dholth, ghaering, r.david.murray, asvetlov, scott.urban
2011-02-18 21:17:23dholthsetmessageid: <1298063843.2.0.816933382266.issue10740@psf.upfronthosting.co.za>
2011-02-18 21:17:20dholthlinkissue10740 messages
2011-02-18 21:17:19dholthcreate