Re: pysqlite design decisions
Christian Boos <[email protected]>
| Newsgroups | gmane.comp.python.db.pysqlite.user |
|---|---|
| Message-ID | <[email protected]> |
glyph-TyWPi3/[email protected] wrote: > ... >> | I've heard, sqlite itself is only middling good at dealing with multiple >> | threads. >> > > >> You heard wrong. >> > > The impression may simply have been garnered from the proximity of threading bugs to database bugs in extremely poorly tested projects such as Trac. > Pleased to hear that ;) Agreed, in Trac we had a bunch of issues with multi-threading, locks, etc. but in the process we also helped to improve the bindings in this area. And I think that with SQLite (>= 3.3.4) and recent pysqlite, the infamous "database is locked" issue doesn't happen anymore in 0.10.2 and 0.11dev, thanks to the ability to pool the connections and reuse them from one request/thread to the next. -- Christian