RE: [sqlite] Bug: Database connection closed on different thread

ct: Re: [sqlite] Bug: Database connection closed on different thread I'm confused with your statement about threads. With multi-core multi-cpu machines becoming more prevalent on the desktop, seems to me that multi-threaded apps would provide better performance (obviously for specific problem

Re: [sqlite] Bug: Database connection closed on different thread

I'm confused with your statement about threads. With multi-core multi-cpu machines becoming more prevalent on the desktop, seems to me that multi-threaded apps would provide better performance (obviously for specific problem sets). Also, don't apps that properly separate UI and background wor

Re: [sqlite] Bug: Database connection closed on different thread

patters <[EMAIL PROTECTED]> wrote: > Greetings, > > We ran into a bug that's not documented behavior: closing a connection that > was created in a different thread (where thread A calls sqlite3_open[16], > "hands off" the connection to thread B, and thread B calls sqlite3_close). > > The documen

[sqlite] Bug: Database connection closed on different thread

Greetings, We ran into a bug that's not documented behavior: closing a connection that was created in a different thread (where thread A calls sqlite3_open[16], "hands off" the connection to thread B, and thread B calls sqlite3_close). The documentation (http://www.sqlite.org/faq.html#q6) says