now I tried with two different handle, one in each thread (and each thread
execute a sqlite3_open), but the insertion fails with : 'database is locked'
error.
I thought this was handled by sqlite since 3.5 version.
http://www.mail-archive.com/sqlite-users@sqlite.org/msg28089.html
http://www.mail-archive.com/sqlite-users@sqlite.org/msg28099.html

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 ?
Do I still have to handle this myself with SQLITE_BUSY tests or mutexes ?

Thank you
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to