"Sébastien Escudier" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > now I tried with two different handle, one in each thread > > In these messages I read : > "with SQLite 3.5, access to each > database connection is serialized. So even though the interface > allows you to have 20 different threads all doing sqlite3_exec() > on the same connection at the same time, the SQL statements are > still being processed one by one" > > Do I misunderstand this ?
How do you think this is applicable? It talks about multiple threads running statements on the same connection, whereas you have two different connections. > Do I still have to handle this myself with SQLITE_BUSY tests or > mutexes ? With multiple connections - yes. See also sqlite3_busy_handler, sqlite3_busy_timeout. Igor Tandetnik
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users