AW: [sqlite] Problems with Multi-Threaded Application.

Use a queue for the database operations in this case. You won't suffer from lock or busy errors, if all access is serialized. Queues can scale very well if done right. Mike -Ursprüngliche Nachricht- Von: Gussimulator [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 12. Juli 2006 20:55 An:

AW: [sqlite] Problems with Multi-Threaded Application.

I would suggest using a queue approach. Its not as bad as it sounds. Have that queue processed by a single thread, which controls the database writes. That way you can save the time for other operations, such as database open/close etc. You can't avoid the "can't read while writing" though.