On Sun, 2008-12-21 at 18:15 +0100, Dirk Meyer wrote: > Last time I checked, pysqlite was not thread safe and every operation > must be called from the thread that created the db.
pysqlite enforces this unless you pass check_same_thread=False when you connect to the db. Then we use a mutex to prevent reentrancy into sqlite itself. That's what r3699 does. I tested the thread-safeness of kaa.db with these changes by spawning 30 threads and having them all add and update objects in a db for a minute. I also tested (somewhat superficially, granted) kaa.epg with the chanes. This fixed some problems that juuva on IRC was experiencing. ------------------------------------------------------------------------------ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
