-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was under the impression that SQLite 3.5.2 is completely threadsafe, meaning you can make any relevant API call in any thread. Examples of things I thought are safe are:
- - Using statements from the same connection in different threads - - Calling step on a statement in one thread and then calling it again in another thread - - Doing some blob i/o in one thread and then doing more in another The FAQ currently says it is somewhat safe. http://www.sqlite.org/faq.html#q6 Is the FAQ out of date? The background is that the wrapper I produce (APSW) has code in it that ensures a connection and all objects derived from it (statements etc) are only used in the same thread. It would be nice to rip all that code out, but if moving/using items between threads could still cause problems then I'll have to leave it in. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHSctTmOOfHg372QQRAvdAAJ4+QVZy0N0SoWQ7jo1mdAKBG1AHMgCeOuvL aQ1y5dYewhzNrukPcNncd/w= =14KI -----END PGP SIGNATURE----- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
