After several experiments and tests, I ended up using one SQLite
connection in several threads. This certainly doesn't currently work
in SQLite natively, but if you properly use some locking mechanism
(CriticalSections in my case), it works fine.
Jiri
You might find that using one thread and accessing the four data sets
sequentially yields you a better result. You will use the one Sqlite
cache and get some benefit from not creating and detroying multiple
caches and connections.
Bharath Booshan L wrote:
Hello All,
I am using SQLite in
Hi Dan,
Thanks for your suggestion.
> If you have any choice in the matter, don't use threads. Run all 5
> queries from the same thread. You can either run them sequentially,
Running sequentially might trouble me as I have to update more sets of
information at a cause of single event.
> or
On Fri, 2007-08-10 at 11:25 +0530, Bharath Booshan L wrote:
> Hello All,
>
> I am using SQLite in one my application and I require to retrieve around
> 4-5 sets of information simultaneously. I have opted to run the queries in
> separate threads which seems obvious choice here.
>
> However, I
Hello All,
I am using SQLite in one my application and I require to retrieve around
4-5 sets of information simultaneously. I have opted to run the queries in
separate threads which seems obvious choice here.
However, I came to know from one of the documents in sqlite.org that single
5 matches
Mail list logo
