Re: [sqlite] MT app using 2.8.14 - collision on sqlite_close() ?

Thanks for the response, Richard. I took a look through main.c, pager.c and os.c and do not see anything that may have caused such behavior. I have tried repeatedly to reproduce the phenomenon and have not been successful (which is good). Looks like I must have had some other issue around the

Re: [sqlite] MT app using 2.8.14 - collision on sqlite_close() ?

I guess what I'm really asking is - are there any circumstances under which SQLite 2.8.14 writes to common (shared among all threads) data structures, either in memory or on disk, during a call to sqlite_close() ? Not that I know of. But I might have missed something. Why don't you check the sour

Re: [sqlite] MT app using 2.8.14 - collision on sqlite_close() ?

Kurt Welgehausen wrote: Perhaps, http://www.mail-archive.com/[EMAIL PROTECTED]/msg02334.html Regards Thanks for the response, however it does not quite fit in with what I saw. I guess what I'm really asking is - are there any circumstances under which SQLite 2.8.14 writes to common (shared am

Re: [sqlite] MT app using 2.8.14 - collision on sqlite_close() ?

Perhaps, http://www.mail-archive.com/[EMAIL PROTECTED]/msg02334.html Regards

[sqlite] MT app using 2.8.14 - collision on sqlite_close() ?

I have a multithreaded application using SQLite 2.8.14. I fully understand, and have implemented, the requirement that each thread make its own call to sqlite_open() to obtain a unique handle to the database. I am using a thread synchronization scheme external to SQLite that has been fully tested