Bob Friesenhahn wrote: > Does anyone have an idea about this specific problem that we encountered? > > It is not clear to me if this is a threading issue, or memory corruption issue
It's probably memory corruption causes by a threading issue. The original mail said: > Any thread may acquire and use this one database connection at any time. Add a mutex. Lock it before beginning _any_ transaction (read or read/write), and unlock it only after the transaction has finished. Alternatively, give each thread its own connection. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
