Meh. sqlite has been threadsafe since 2006, and the python adapter still won't let you use connections across multiple threads because you might have an old version.
You're using an explicitly unsupported workaround (check_same_thread=False) that may cause dataloss due to optimisations in python 2.6 and later. See http://bugs.python.org/issue3846 I guess your workaround coupled with the mutexes should be a safe solution but may not be the most performant. I'm still researching and trying to wrap my head around the weirdness that is the python sqlite3 adapter though. It does some *strange* things. The ruby adapter is threadsafe. Just sayin.. ;-) -- | Steven Pinkham, Security Consultant | | http://www.mavensecurity.com | | GPG public key ID CD31CAFB |
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
