My main complaint with it is the way it delays and modifies user transactions. I’m guessing this is in an attempt to prevent deadlocks, which are easy to produce *if* you don’t understand sqlite’s concurrency model. Unfortunately, I found that pysqlite’s modifications were doing more harm than good in my application, which makes extensive use of concurrency and is not able to tolerate multi-second timeout delays.

I’m comfortable with sqlite’s concurrency model (it’s not hard!) and so made much better progress by managing it myself. In this case, all of my transactions are designed to be very short-lived (as they always should be) and so sqlite handles it without additional ‘trickery’.

I’d like to know your thoughts on how best to support this, however. Autumn’s development is ramping up and if I were to support this I prefer to do so early on.

Thanks!