In the source code at the begin of the two processes that execute queries on
the database I've used the code:
srand(time(NULL));
to avoid collisions...
(I never started the two processes at the same instant)
That should work great.
>>
>> http://www.sqlite.org/capi3ref.html#sqlite3_busy_timeout
>>
>> If this does not fix your problem, it is possible that an application has
>> a read lock permanently open. Check that your readers are not doing a
>> begin without a commit.
>
> That was my thought too. It sounds like something else has the file
> locked.
>
> Laura is there a backup program that might be reading your database
> and locking it?
Only my two processes execute queries on the database and no other
program...
Is there any other way to be sure of this? Can you suggest me a test to do
when the lock will happen again to have more info?
Do you have the 'fuser' command in your flavor of linux/unix?
http://linux.about.com/library/cmd/blcmdl1_fuser.htm
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
