Re: [sqlite] Transaction journal corrupted by antivirus

2007-05-03 Thread Voxen
--- We're Hiring! Seeking a passionate developer to join our team building products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -Original Message- From: Voxen [mailto:[EMAIL PROTECTED] Sent: Thursday, May 03, 2007 2:58 AM To: sqlite-users@sqlit

[sqlite] Transaction journal corrupted by antivirus

2007-05-02 Thread Voxen
" has been found in "C:\Documents and Settings\Voxen\Application Data\MyApp\mail.db-jounal" file. This means the antivirus found a virus in the transaction journal file and removes it. Its altering the journal file and then produces a SQLITE_MISUSE error. How can I work ar

Re: [sqlite] Re: Re: Question about multithreading

2007-03-22 Thread Voxen
There's no "like" - you do use connection pointer directly from thread B. The fact that the piece of code thread B currently executes is a method of an object that happened to be created by thread A is immaterial. Thanks Igor. That clears things and it shows me I need to open/close the data

Re: [sqlite] Re: Question about multithreading

2007-03-22 Thread Voxen
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

Re: SPAM: [sqlite] Re: Question about multithreading

2007-03-22 Thread Voxen
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

[sqlite] Deadlock with multiple threads

2006-10-02 Thread Voxen
eadB (or ThreadC) it doesn't happen, so I'm wondering if there is an issue with threads creating other threads that open sqlite connections. Thanks Voxen - To unsubscribe, send email to [EMAIL PROTECTED] -