Ed Pasma wrote:
However, it would be too time consuming to serialize every call to
sqlite3_step(), so I wonder whether it can be called in another
thread.
This almost immediately raises
"library routine called out of sequence". It occurs as soon as the
processing of A and B overlap, that means A is preparing statement #2
while B is still executing #1.
Have you tried using Mutex or some other way to prevevent really
simultaneous calling of SQLite methods? My guess that it should work
well then, but I haven't tried it myself...
Yes I did the same experiment with a lock that made thread A wait until
B was finished. So actually only one thread can be active at the time.
I don't see how the outcome of this experiment can be of any interest,
as there is no time reduction any longer. But your guess is right that,
it works.
How would multiple threads be faster than a single one when you are
accessing a single resource?
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
