Re: [sqlite] Threading (again)

SQLite is completely threadsafe. So we can share a single database connection across threads, it the underlying OS is Okay. But I guess we can not share a sqlite3_stmt prepared statement across threads threads. Am I correct. Or am I missing something? -- Sabyasachi

Re: [sqlite] Threading (again)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 D. Richard Hipp wrote: > SQLite is completely threadsafe in 3.5.2. But that does not mean > that running SQLite will magically fix threading bugs in Linux 2.4 > kernels or in GLIBC. The FAQ warns you to beware these problems. Thanks for the

Re: [sqlite] Threading (again)

On Nov 25, 2007, at 2:21 PM, Roger Binns wrote: I was under the impression that SQLite 3.5.2 is completely threadsafe, meaning you can make any relevant API call in any thread. Examples of things I thought are safe are: - - Using statements from the same connection in different threads - -

Re: [sqlite] Threading (again)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roger Binns wrote: > I was under the impression that SQLite 3.5.2 is completely threadsafe, > meaning you can make any relevant API call in any thread. I should be clearer what I meant by threadsafe. The most important notion is that there is no

[sqlite] Threading (again)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was under the impression that SQLite 3.5.2 is completely threadsafe, meaning you can make any relevant API call in any thread. Examples of things I thought are safe are: - - Using statements from the same connection in different threads - -