Ticket #109 (defect)
Opened 3 years ago
Last modified 3 years ago
Concurrency failures with SQLite3 2.3.2
Status: closed (fixed)
| Reported by: | Delaney | Assigned to: | fumanchu |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.0 |
| Component: | Storage | Keywords: | |
| Cc: | Estimate (total hours): | ||
Occurs when quickly refreshing browser or running apache bench with multiple threads (-c5 in this case). Setting 'store.db.threadsafe = False' just after storage.resolve appears to fix problem but shows SQLite's connection pools are not working as expected. Tests were done on XP64Pro with fresh install of Python 2.5.4 using built-in sqlite3 2.3.2.
Ticket requested by fumanchu
Change History
01/21/09 19:24:12: Modified by delaney
02/04/09 17:40:39: Modified by fumanchu
- status changed from new to closed.
- resolution set to fixed.
More possible explanation to why this is happening. http://www.mail-archive.com/django-developers@googlegroups.com/msg19006.html
The fix that's in PySQLite 2.5 http://oss.itsystementwicklung.de/trac/pysqlite/changeset/337:80ee6488cb53