[EMAIL PROTECTED] wrote:
On Feb 7, 2005, at 9:50 AM, Yogesh Marwaha wrote:
Both threads are using same sqlite connection.
This is your problem.
Each thread should use an isolated connection.
Correct me if I am wrong but I was under the impression that having 2 separate
connections to database (and while on subject I noticed that making connection
via ADO.NET takes significant time measured in seconds rather than in milliseconds)
will result in locking issues that I found I could not recover from, ie reconnecting
to database fails as it is still locked.
My solution was to use single connection in a C# wrapper around ADO.NET
that would queue requests using primitive locking to avoid actual locking of database
and it can recover from "library called out of sequence" errors.
Now I have two questions:
1) is it better using multiple connections to the same database (surely locks will be issue?)
2) a friend of mine voiced opinion that it is a good idea to open source my wrapper (C# .NET
on top of ADO.NET), is there a need in it?
regards,
Alex
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.5 - Release Date: 03/02/2005
