Re: [sqlite] Moving database connections across threads

are correctly controlling access to this connection with our own mutexes. Is that right? Thanks, Mark -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 6:54 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Moving database connections across

RE: [sqlite] Moving database connections across threads

mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 19, 2007 6:54 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Moving database connections across threads > > > The underlying issue with thread misbehaviour is that POSIX > file locks > are process specific, not

Re: [sqlite] Moving database connections across threads

The underlying issue with thread misbehaviour is that POSIX file locks are process specific, not thread specific requiring some tormented logic . You only need the POSIX locks if you have multiple access to the same database and are writing to the database. If you have a multi-threaded

[sqlite] Moving database connections across threads

Hi- We have an application that wraps SQLite 3.4.1. Due to some vxWorks platform issues with non-standard posix behavior, we are considering compiling SQLite with THREADSAFE = 0, and then having our application make sure that only one thread can access SQLite at a time. I was wondering about