Gil:
In you threads, dont declare sqlite3 *db private or public, instead
make it a local variable in each method. Then if one class calls a
method from another, a seperate database pointer will exist (on each
threads local stack) and you will have no problems. Let me know how
it works.
--
Ri
On 3/22/07, Igor Tandetnik <[EMAIL PROTECTED]> wrote:
Gil Delavous <[EMAIL PROTECTED]>
wrote:
> However, what happens when a thread calls a method from the main
> thread, this one using its own sqlite connection?
The question doesn't make any sense to me, sorry. Methods don't belong
to threads.
Hi Igor,
Thanks for you reply. I might have confused things, sorry about that.
So, from my example, let say thread A created the object "main", and
thread B created the object "print".
When thread B calls the method from object "main" (as shown by the
example), my question was to know if t
Gil Delavous <[EMAIL PROTECTED]>
wrote:
However, what happens when a thread calls a method from the main
thread, this one using its own sqlite connection?
The question doesn't make any sense to me, sorry. Methods don't belong
to threads. Any function in a program can, in principle, be executed
4 matches
Mail list logo
