On Thu, 10 Jun 2004, Drew, Stephen wrote:
>Tito,
>
>Thanks for that. I've had a look but it doesn't really help. The two main
>questions are:
>
>1.)Why do I need a separate sqlite pointer for each thread, if I am
>protecting access to it?
I've always wondered that. I can't think of a reason
Tito,
Thanks for that. I've had a look but it doesn't really help. The two main
questions are:
1.) Why do I need a separate sqlite pointer for each thread, if I am
protecting access to it?
2.) Even aside from this, I am using multiple threads to access the
database, each opens it when it
Hi Stephen,
Check this: http://www.sqlite.org/cvstrac/wiki?p=MultiThreading
Regards,
-- Tito
On 10 jun 2004, at 17:05, Drew, Stephen wrote:
From the SQLite FAQ:
"Threadsafe" in the previous paragraph means that two or more threads
can
run SQLite at the same time on different "sqlite" structures
>From the SQLite FAQ:
"Threadsafe" in the previous paragraph means that two or more threads can
run SQLite at the same time on different "sqlite" structures returned from
separate calls to sqlite_open(). It is never safe to use the same sqlite
structure pointer simultaneously in two or more
4 matches
Mail list logo