This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author takluyver
Recipients Dave Sawyer, berker.peksag, docs@python, orsenthil, takluyver
Date 2016-06-02.21:39:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464903561.59.0.0560939318757.issue27113@psf.upfronthosting.co.za>
In-reply-to
Content
Having watched the video of Dave's PyCon talk (thanks Dave), I think he's talking about using locking to control transactions, which presumably the sqlite bindings don't handle by themselves. But I don't *think* you need manual locking just to maintain database integrity. If that's the case, it's probably helpful to clarify it.

I'd probably suggest that if you want to write from multiple threads and control transactions (i.e. more than just individual INSERTs fired from different threads), it's probably easier to use separate connections and let sqlite handle the synchronisation than to synchronise them yourself.
History
Date User Action Args
2016-06-02 21:39:21takluyversetrecipients: + takluyver, orsenthil, docs@python, berker.peksag, Dave Sawyer
2016-06-02 21:39:21takluyversetmessageid: <1464903561.59.0.0560939318757.issue27113@psf.upfronthosting.co.za>
2016-06-02 21:39:21takluyverlinkissue27113 messages
2016-06-02 21:39:21takluyvercreate