On Nov 3, 2008, at 9:54 AM, Ken wrote: > No I would not wrap the querries in a transaction. > > I think the problem you are encountering is due to thread > interaction upon the sqlite structures. Since it was compiled with > THREADsafety disabled. > > If you have two threads that share the same connection. You need to > compile with THREADSAFE turned on. Or provide your own mutexing such > that neither thread interacts with the sqlite connection concurrently.
Note: when SQLITE_THREADSAFE=0 then it is not safe for two threads to call SQLite under any circumstances, even if they are using completely separate database connections. My advice is that you not use threads. Threads are evil. But, recognizing that you are unlikely to heed this warning, at the very least compile with SQLITE_THREADSAFE=1 if you really think you must use threads. D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
