Thorsten Kersting <[email protected]> wrote:
> I try to write into a database with multiple processes, which can not
> communicate to one another, beacause i start one programm many times.
> When the program should write, it returns sqlite_busy. that i
> understand. but then, every process return sqlite_busy, and it seems
> they are blocking themselves, and the programm is stuck in an endless
> loop.

http://www.sqlite.org/c3ref/busy_handler.html

the part about a deadlock.

If you have explicit transactions that start with a SELECT and later perform 
INSERT or UPDATE or DELETE, initiate such transactions with BEGIN IMMEDIATE 
statement. This lets SQLite know that the transaction intends to write at some 
time in the future, which allows SQLite to avoid deadlock situations.
-- 
Igor Tandetnik

_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to